Yes, 3.1 supports this as well. Although, I believe what Scott is referring to is defining a source path that is outside the path of workspace, but perhaps I am wrong. -Jason

This breaks the source navigation in eclipse when you don't have the variable defined or the project downloaded. It even breaks this navigation on projects that are not affected by the sourcepath. I just remove these sourcepaths so I can actually use the editor to do things like "open declaration". What is really required in eclipse is a way to attach a path to a sourcepath (locally) without modifying the project defintion that will break other developers. On Mon, 2006-08-28 at 15:54 -0500, Scott M Stark wrote: > So as an example, I did the following: > > 1. In the thirdparty/jboss/microcontainer folder, create a folder and > use the advanced settings to select "Link to folder in the file > system" option. > 2. Created a JBOSSMC_SRC path variable that pointed > to /home/svn/JBossMC/jbossmc where I have the trunk jbossmc checked > out > 3. Selected the Variable... option for the link and Extended the > JBOSSMC_SRC to point the link to the container/src/main directory. The > link directory was named container-src so the added directory was > thirdparty/jboss/microcontainer/container-src. > 4. Set the referencing project build path entry for the > jboss-container.jar to use a workspace source folder > of /thirdparty/jboss/microcontainer/container-src > > The resulting jmx/.classpath entry was: > > <classpathentry > sourcepath="/thirdparty/jboss/microcontainer/container-src" kind="lib" > path="/thirdparty/jboss/microcontainer/lib/jboss-container.jar"/> > > This is independent of the filesystem and even the path variable > name. > > Now the next issue is that the source path is only associated with the > jmx project. I don't want to have to set the source path for every > project that includes the jboss-container.jar in its path. I tried > adding a jboss-container user library, but I can't set the jars > relative to a classpath/path variable so its back to a system path > specific settings. > > Carlo de Wolf wrote: > > Ehr... it is possible: > > > > 1. create a project; > > 2. create a new file within that project as a 'link to file' using an > > extension of a path variable; > > 3. use that file as a source attachment. > > > > Carlo > > > > On Fri, 2006-08-11 at 06:45 -0500, Scott M Stark wrote: > > > > > Yes, what I'm looking for is an ability to set the source path for any > > > library jar in the Java Build Path/Libraries settings of a project > > > relative to some workspace/env variable like ${SVN_HOME} so that the > > > project can more easily be re-targeted when I use it on a different system. > > > > > > > > > Jason T. Greene wrote: > > > > > > > Yes, 3.1 supports this as well. Although, I believe what Scott is > > > > referring to is defining a source path that is outside the path of > > > > workspace, but perhaps I am wrong. > > > > > > > > -Jason > > > > > > > > > > > > > > > _______________________________________________ > > > jboss-development mailing list > > > jboss-development(a)lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/jboss-development > > > > > > > _______________________________________________ > > jboss-development mailing list > > jboss-development(a)lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/jboss-development > > > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development