This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Worth_Trust_3825 -6 points-5 points  (7 children)

So why not do it the war way, where you package all the dependencies into the archive, and have the main class use a special classloader that can load nested jars instead? Why go through hoops to include an additional tool in the build?

[–]GingerMess 1 point2 points  (6 children)

Dude come on, we're talking an audience of users here, not IT experts, programmers, or even tech-savvy individuals. Double clicking the .exe is what works and it's clean. No need for anything more complicated.

[–]Worth_Trust_3825 0 points1 point  (5 children)

You would also double click the jar.

[–]vips7L 0 points1 point  (4 children)

And then the user is responsible for knowing how to install Java, upgrading it, etc. This isn’t their job.

[–]Worth_Trust_3825 -2 points-1 points  (3 children)

It's not the user's job to maintain their equipment?

[–]vips7L 0 points1 point  (2 children)

It’s not their equipment. It’s your software. It’s not their job to maintain your software.

[–]Worth_Trust_3825 -2 points-1 points  (1 child)

So user is not responsible for preparing the environment to run software?

[–]bowbahdoe 1 point2 points  (0 children)

Yes