The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.
Rob Phair wrote:Thanks for the quick reply, Tim. So, if I understand your reply correctly, you're saying that each project has a build classpath, and when a run configuration is created, the run configuration's classpath includes all entries on the project build classpath, plus any additional entries that you define in the run configuration interface?
Rob Phair wrote:
As I understand it, when you export an executable .jar file from Eclipse, you provide a run configuration, which supplies the .jar file with appropriate metadata. What I'm seeing now is that, when I have that external class folder defined on my build classpath, that folder does not get included in the export. That may be because there's only configuration information in the folder; no actual .class files exist here, so it's not really a "class" folder, per se. Regardless of whether I choose the "Extract required libraries into generated JAR" or the "Package required libraries into JAR" option on the Eclipse .jar export dialog, I still fail to see my configuration folder included in the .jar file.
My new question, then, is, can I include a folder containing non-Java files (.xml, .properties, etc.) in a .jar file using Eclipse's .jar export dialog? I think that, if I can get the config folder into the root of the .jar file, I might be able to get this to work. Is there any way to force Eclipse to include a specific folder structure as part of the archive when exporting .jar or EAR/EJB files? Simply including the folder on the build path doesn't seem to work.
Thanks again for any help you can offer!
No, tomorrow we rule the world! With this tiny ad:
Master Gardener Programhttps://coderanch.com/t/771761/Master-Gardener-Program