It should be quite straightforward to run your application from an IDE with some maven support (Eclipse, IntellIJ). These IDE's will take care about creating the correct classpath.

If you want to do this manually, try this:

change to the directory that contains the pom.xml execute the maven command:

mvn clean install

This will compile your project and create the jar you defined in the pom.xml file. It runs the maven phases clean and every phase up to install (compile, test, etc).

Then collect all jar files you use as dependencies (required to run your project):

mvn dependency:copy-dependencies

This executes the dependency plugin which will copy all dependencies into target/dependency.

You can then run your main method using:

cd target/
java -cp TCPPing-0.0.1-SNAPSHOT.jar:dependency TCPPing

-cp defines the classpath (all locations / jar files / folders that contain classes). TCPPing is the class your run that has a main method.

Note the : is for Linux / Mac - I think windows uses a ;.

You can run mavan spring-boot project using the following command

mvn spring-boot:run

Backslash means the command continues to the next line (if you have a newline character). https://stackoverflow.com/a/14681059

You can simple enter mvn archetype:generate in terminal and you will be asked to enter groupId, artifactId etc. See please example.

There is Maven build plugin that would bundle all your dependencies in a JAR. You could execute it simply with

java -jar mybundled.jar

without caring about class path dependencies.

And here comes the Maven plugin. Replace the MainClass with your entry point.

<plugin>
   <groupId>org.apache.maven.plugins</groupId>
   <artifactId>maven-assembly-plugin</artifactId>
   <version>2.4.1</version>
   <configuration>
      <descriptorRefs>
         <descriptorRef>jar-with-dependencies</descriptorRef>
      </descriptorRefs>       
      <archive>
        <manifest>
          <mainClass>com.yourdomain.Main</mainClass>
        </manifest>
      </archive>
     </configuration>
    <executions>
      <execution>
         <id>make-assembly</id>
         <phase>package</phase>
         <goals>
           <goal>single</goal>
         </goals>
       </execution>
    </executions>
</plugin>

As it is bound to the package lifecycle, you would find your bundled JAR in your target directory after doing a ...

mvn package

Regarding your concern that your code won't run on another machine, Java is platform-independent and generally you can rely on that. However, three things come to my mind that can make life hard:

1. Your code depends on the system encoding. Maven should give you a warning on that in the log, advising you to specify it explicitly.
2. You interact with the runtime, like executing system commands. ps won't work on windows and dir /s probably not on *nix.
3. The version of your Java environment differ. Of course, JavaFX code won't run with a Java 1.5. If you use the latest features, make sure your clients already have the respective version or, at least, are able to get it from somewhere. You might want to take a look at the source and target compile options, too: http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javac.html#crosscomp-example