Re: [JBoss-dev] Leading slashes on jars in build path

2006-06-26 Thread Scott M Stark
] 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

[JBoss-dev] Leading slashes on jars in build path

2006-06-24 Thread Tim Fox
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

Re: [JBoss-dev] Leading slashes on jars in build path

2006-06-24 Thread Adrian Brock
The leading slash is relative to the eclipse workspace not the file system. Do you create a simple project called thirdparty in the workspace based on what the build/build-thirdparty.xml creates? On Sat, 2006-06-24 at 15:10 +0100, Tim Fox wrote: I've noticed that some (most?) of the library

Re: [JBoss-dev] Leading slashes on jars in build path

2006-06-24 Thread Tim Fox
Yes, I've got a project called thirdparty at the same level as all my other projects (jms, messaging, connector etc). It's weird, as I say, if I remove the leading slash then everything works ok. Adrian Brock wrote: The leading slash is relative to the eclipse workspace not the file system.