Monday, 15 February 2010

java - Using Eclipse "export as Runnable Jar" without configurations -


The way I am using Eclipse, there should be something wrong, so explain to me: I have a The folder has been marked as src for my configuration in the classpath to be properly deployed while compiling my project. It works fine because IDEs work well in debugging / running. But if I export the project as a runan jar file, then the config files are embedded in it, and as a result I do not allow the user to change the configuration (I have to manually remove the file from jar and get desired Existing Dior to achieve behavior) Is there some solution to automate it? I did something like that: exported as "Exportable as JNR Runnable" as an ANT file, then I was manually modified to do this work, but unfortunately I have to manually update the file when class The path will change. Any suggestions?

When you select the export option, in the eclipse, you will see the JAR file, the Jawadok and the Runnabal JAR file You can use the JR file option, where you can select / deselect the classpath along with the project? There is also an option to select only class files without resources. Hopefully the option will be useful


No comments:

Post a Comment