It's not what your program can do, it's what your users do with the program.
Joe Areeda wrote:Is there a way to specify a class path when you're using .jar files or do I need to write my own class loader?
Stephan van Hulst wrote:Why not distribute it as an archive with a structure like this:
Make a jar out of the network library for every os, and distribute it with your archive. In the application shortcut, you can just run the application like this: "java -cp lib/* com.example.MyMainClass"
If you don't want to use a shortcut because you don't have java.exe on your PATH, you can add lib/* to your executable jar's manifest file's classpath, and run your jar directly.
It's not what your program can do, it's what your users do with the program.
Paul Clapham wrote:I think you're mixing up the problem of how to structure your applications (e.g. what Stephan described) and how to install them. I tend to be of the opinion that you should use Java Web Start to install your applications, and when you do that, the question of how to organize the jar files kind of goes away.
It's not what your program can do, it's what your users do with the program.
Hug your destiny! And hug this tiny ad:
We need your help - Coderanch server fundraiser
https://coderanch.com/wiki/782867/Coderanch-server-fundraiser
|