Community
Participate
Working Groups
We are using clearcase dynamic views. It would be nice to get the output folder out of the dynamic view to improve build times. The project files are themselves in clearcase and we use Eclipse on both Solaris and Windows. I want to create a linked folder for the build output in a platform independent way. So the path needs to be relative to something and the workspace root would be a good choice. Maybe you could give us a predefined "core variable" for the workspace root.
Suggest this is closed. Requested feature is implemented in 200301281500. Thanks very much
Whoops I got ahead of myself there! I still need a predefined path variable for the workspace root. I thought you had added one but it turned out to be one I added manually to my workspace a while back.
If anybody else is interested in this, I've made my own plugin to do this. It can be downloaded from http://neil.swingler.name/eclipse/name.swingler.neil.workspaceroot.zip It defines the WORKSPACE_ROOT path variable. The workspace provides a handy "per workspace" working area for intermediary files like class files. By compiling to the hard disk rather than a clearcase dynamic view, we have reduced build time from 8 minutes to 2.
This is why I don't want to add this default variable. Using the workspace root location as a scratch location for various linked files is dangerous. If you were to later create a project in the default location whose name matched the named of a folder that is linked there, you could run into problems. This is especially true for build output locations, which can be scrubbed (deleted) at any time by the java builder. Basically, if you need a local location to put things in, the workspace location isn't the best choice. You'd be better off using a subdirectory of System.getProperty("user.home") as a scratch location.
I take your point. Although I think people have got to know what they are doing when they use these linked resources. After all the same problems can be achieved without using a variable. The other choices I have at the moment for a "per workspace" working area would be: o home directory - might be a networked drive o temp - a bit too temporary o special subdirectory of workspace For the first 2 I would also need some way to uniquely identify a workspace other than it's path. BTW we use a different workspace for each branch of the code we are working on and several may be in use concurrently.
Marking old enhancement requests that we don't intend to fix in the near future as RESOLVED LATER. This does not mean we will never do them, but it means we have no specific plans to address them.
*** Bug 33957 has been marked as a duplicate of this bug. ***
reopening to mark as dup
*** This bug has been marked as a duplicate of bug 122945 ***
