[JBoss-dev] How to portably define source locations for library

[Carlo de Wolf]

In Eclipse 3.2 you can have a workspace relative path as sourcepath.
Haven't checked Eclipse 3.1.

Carlo

On Thu, 2006-08-10 at 00:31 -0500, Jason T. Greene wrote:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=44001
> 
> Basically the only solution to this problem is to define all classpath
> libs as variable entries, and this will allow variable source
> associations.
> 
> -Jason
> 
> > -----Original Message-----
> > From: jboss-development-bounces at lists.jboss.org
> [mailto:jboss-development-
> > bounces at lists.jboss.org] On Behalf Of Scott M Stark
> > Sent: Wednesday, August 09, 2006 6:26 PM
> > To: jboss-development at lists.jboss.org
> > Subject: [JBoss-dev] How to portably define source locations for
> library
> > 
> > Some of the jbossas projects have source locations for the thirdparty
> > library jars, but these are full operating system specific source
> paths.
> > Is there a way to use a workspace variable that defines the root of a
> > path so that these project definition can be shared by setting the
> root
> > where source is being checked out to?
> > _______________________________________________
> > jboss-development mailing list
> > jboss-development at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-development
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development