That happened to me a lot of times when I started writing java distributed applications.
Check your project build path (since you're using eclipse, right-button click on your project's folder, then Build Path > Configure Build Path). If any of the paths that are specified there are custom *ie C:\User\daMachineMaster\Java\jre\bin
or whatever, it won't work on any other machine because the application will always look for that path, which won't exist in no other machine than daMachineMaster
's computer. You could use a wrapper to fix this issue, since it encapsulates all needed information in a .exe, for example.
If that still isn't your issue, search your code for any links to your local directories. For example,
String style = main.screens.ScreenFramework.class.getResource("C:\Users\Dwayne\Music\cool\DarkTheme.css");
After you've located these kinds of hard links, the solution is changing them to be relative links. Check How to define a relative path in java
In the above case, it would mean changing to something like:
String style = main.screens.ScreenFramework.class.getResource("DarkTheme.css").toExternalForm();
Also, as mentioned in other answers, check if the other computers hava java installed. I don't think that they need any environment variables defined to run a runnable jar but if you want to run your app in the cmdline with something like java -jar yourapp.jar
then you need to go to the windows explorer (assuming you're using windows), right-click Computer, then click Advanced System Settings > Environment Variables > New... > Variable Name = JAVA_HOME; Variable Value = directory where java is installed > OK > Click on PATH > Edit... > add JAVA_HOME\bin to PATH > OK