I see similar issues. I just updated the jbossmc checkout which includes the container project. I'm seeing the following error in the Problems panel:
Severity Description Resource In Folder Location Creation Time 2 Project container is missing required library: '/thirdparty/jboss/common/lib/jboss-common.jar' container June 26, 2006 8:58:30 PM Even though the thirdparty project does include jboss/common/lib/jboss-common.jar, and the container Java Build Path refers to thirdparty/jboss/common/lib/jboss-common.jar and shows as valid. It seems like this is due to the projects workspace being out of date. If I go and update (F5) each project the error clears. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tim Fox Sent: Saturday, June 24, 2006 7:10 AM To: jboss-development@lists.sourceforge.net Subject: [JBoss-dev] Leading slashes on jars in build path I've noticed that some (most?) of the library entries on the Java build path (Eclipse) for many of the projects start with a leading slash: /thirdparty/jboss/profiler/jvmti/lib. This means on my system that the libraries cannot be found since I do not checkout jboss head into the root of the volume. So, every time I update from CVS I have to remove all the leading slashes so eclipse relative to the top of my workspace where the libraries will be found. Is there any reason for having the leading slashes? Or perhaps I am doing something wrong and somehow I can get eclipse to interpret the leading slash as being at the root of my workspace. Any ideas? Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
