executable-jar

I'm trying to use Maven to create an executable jar file that includes the dependencies in a separate directory. I've seen a lot of questions on SO about creating an "uberjar"--I don't want that. What I want is to have the depenedencies copied into a "lib" directory like so (and the jar MANIFEST.MF file with a ClassPath entry that points to them): /myApp myApp.SNAPSHOT-1.0.jar /lib hibernate.jar log4j.jar ... As an added bonus it would be nice if I could copy /src/main/resources/* into /myApp/conf and then zip up the entire /myApp directory into myApp.zip as well. EDIT: I use the maven

I've written a small application. I've put the database specific information in a properties file. db.url=jdbc:mysql://localhost:3306/librarydb db.user=root db.passwd=pas$w0rd When I build the application to get the executable jar file, the properties file gets included inside. The whole purpose of putting those information in a properties file is to allow the user to change those but this is making it impossible. How can I include a properties file with the jar file not in it? Kinda like you do with AppSettings file in .NET applications. I'm very new to Java so I'd appreciate if you could

Is there any way I can make an executable .jar that will open up the command line when double clicked? I'm making a text-based adventure game. As of right now it is just a maze with rooms. Eventually it is going to be much bigger and more in depth but for now I just want to get the basic structure down. Anyways, to make this work I've been getting output and input from the System.out.printf command and the java.util.Scanner. It's all working beautifully so far but I've realized I'm going to run into a problem when I try to send this to other people that don't know how or just don't want to run

What is the best way to set the target package for an SBT project to be an executable jar file? It would need to bundle scala-library.jar and set the manifest for main-method. Thomas Lockney Use the assembly-sbt plugin (originally created by Coda Hale, now maintained by Eugene Yokota ): https://github.com/sbt/sbt-assembly Once you add this to your project it will build a so-called "fatjar" which is executable via java -jar projectName-assembly.jar . It will autodetect your main method -- if there is more than one in your source, you can explicitly set which one to use by setting mainclass , e

Recently have been touched Java classloaders and suddenly recognized that do not fully understand what happens step-by-step when someone calls java -jar App.jar Well I guess a new instance of JVM is created it uses ClassLoader to load main class and other classes byte-code is started to execute from main() method But still I suppose there are many things I need to know more about it. Who and how decides which classes should be loaded at startup and which once needed? I have found two related questions but there it is not explained how to apply that to Java realities. What happens when a