If I add JARs to the SlickEdit class path using
Add Jar Wildcard..., it always includes all JARs in all subdirectories below the selected directory. This causes compile problems and makes my classpath dramatically longer.
Once I tracked down the problem, I reproduced it this way:
- I created a directory structure containing JARs in its root and in its subdirectories.
- I placed this new directory on a drive other than the drive containing my SlickEdit project.
- I added the new directory to the SlickEdit class path using Build->Java Options, on the Classpath tab, using the Add Jar Wildcard... button. I made sure the Recursive check box was deselected.
- I invoked project-compile, using a keyboard shortcut. I captured the command line that wrote to the build window. (Because the JARs were on a different drive, project-compile listed them explicitly on the command line instead of listing them in its temporary JAR file.)
The JARs in the subdirectories were explicitly listed on the command line.
I would prefer that you didn't touch my classpath. However, if you do something with my classpath, you MUST let me know what you are doing. When I run into problems, visibility into what is happening can help me understand what is going wrong. Just as importantly, it will help me understand if the bug is mine or SlickEdit's.
