| Could there be a "preference" that tells wolips to not step on my classpath and add things to it I don't want and there is no way to get rid of?
If you have something like ERExperimental and there is another version of ERExperimental that you want, you have to close the ERExperimental project, or delete it from the workspace, or switch workspaces--just to get the correct version on the classpath.
This is also a problem with maven, as it wants to setup the classpath as well.
On Sep 21, 2012, at 9:53 AM, Patrick Robinson wrote:
Look at your Build Path (ctrl-click on the project -> Build Path -> Configure Build Path. Click Add Library, select WebObjects Frameworks, then click Next. This will show you what frameworks have been added (and is where you can add others), and it shows the location where it's finding each framework, whether Project, Local, or System.
It appears that WOLips prefers to find frameworks in Projects, then Local, then System. That is, if you have a JavaWOExtensions framework project open in Eclipse, then it'll use that. Otherwise, if it finds one in your "Local Frameworks" location (as defined by your WOLips properties file), it'll use that. Lastly, it'll look in the "System Frameworks" location.
It seems we should have some say as to what goes on the classpath, but our say is overridden, and I don't know a way around it.
Mr. G Brown
|