Community
Participate
Working Groups
In Eclipse release 3.0.1, the WebTools project would like some additional function enabling linked resources within the workspace. 1) Support linking of resources and folders to resources existing inside the workspace. 2) If linked resources originate within a java project, optional turn off pushing output to linked target (compiled files) Will want to compile in linked location (or both). (linked location will have seperate output folder). 3) Recognize existing links of source files/folders and optionally provide actions on linked locations. Use case 1 (Simple folder linking) EARProject1 ejbjar1srcfolder -> links to src folder in EJBJar1 project web1srcfolder -> links to Web1 project folder web2srcfolder -> links to Web2 project folder Use case 2 (Mix of folder/resource links) SimpleProject1 javasrc ejbsource -> links to src folder in EJB1 project Class1.java websource webpackage -> links to package in Web1 and Web2 projects Class2.java -> links to file in Web1 Class3.java -> links to file in Web2 webcontent samp1.jsp -> links to file in Web1 samp2.jsp -> links to file in Web2 j2eecontent META-INF -> links to folder in EJB1 ejb.xml WEB-INF web1.xml -> links to file in Web1 web2.xml -> links to file in Web2
Unless I misunderstand, Use Case 1 is already supported with linked resources. Use case 2 will not be supported for 3.0.1.
My bad - I meant 3.1 timeframe So we can link existing folders inside the workbench to folders in another project? I didn't realize (I thought we only supported linking to files/folders outside the workspace).
The two main restrictions on linked resources are: - you can't link a parent or child of the project that will contain the linked resource (i.e., create loops in the resource tree). - linked resources must be direct children of projects. You may be interested in reading: http://www.eclipse.org/eclipse/development/flexible-projects-proposal.html
Can I summarize your request as wanting to remove the current restriction that linked resources must be direct children of a project?
Please reopen when feature request is clarified.
I have a few more comments that may help clarify our request. When a user opens a linked resource to another that exists in the workspace, this file is treated as a different IFile instance. (Two editors can be opened on same file, but different projects). This is tied to another request of CVS decorators be applied to linked resources if the target is under CVS control. Additionally - we would like the ability to link folders not directly under the root.
*** Bug 77485 has been marked as a duplicate of this bug. ***
Moving confirmed bugs/enhancements out of the "inbox"
*** Bug 61011 has been marked as a duplicate of this bug. ***
Updating summary to provide a more accurate description of this request.
Target for M4.
Support for linked resources at arbitrary depth has been released. There are a few UI issues remaining that are described in bug 116924.
*** Bug 127127 has been marked as a duplicate of this bug. ***
