Community
Participate
Working Groups
I'd like to use TPS files to manage projects, but need to be able to specify the target directories to which the projects are checked out to due to team- specific source policies. I'd like an option in the TPS import wizard to specify the target directory, just as in the new Java project wizard, a different directory can be specified.
Given the current API, we couldn't do this genrally for all providers. We could do it for CVS but it would be a bit clunky to prompt for the localtion for each project being imported.
What about just prompting once for the base location from which project directories are created? I imagine now it defaults to workspace root...
Yes, that would probably be enough for most users. A workaround would be to open Eclipse on a workspace that is rooted at that folder. I understand that this doesn't work if you need projects rooted in two different places but in may help in some cases. There is currently no plan to address this but patches will be accepted.
*** Bug 288588 has been marked as a duplicate of this bug. ***
*** Bug 295243 has been marked as a duplicate of this bug. ***
*** Bug 308753 has been marked as a duplicate of this bug. ***
here are my 2 cents on this which might just serve as a clarification of previous comments: there 2 levels of granularity to be be considered here IMO as others have pointed out: a) put all projects in the PSF file into the same folder (customizable location) b) open a detailed mapping dialog page that lets you chose per repository path prefix a location (is this meant by "base location" in #2?) to illustrate: - you have a product B that is based on another product A - both are in the same repository but in diff. location e.g. https://my.svn.com/svn/A/trunk and https://my.svn.com/svn/B/trunk - I usually would want to have the respective bundle projects for each path prefix in diff folders. doing the mapping per path prefix lets the user define arbitrarily fine grained target folders. there could be some wizard button to detect the most common mappings schemes and fill up the mappings, e.g. like the one outlined above. as an extension to this: it might be a good idea to be able to share and save such a mapping scheme in case there is a policy in place and all team members have to do this. in that case the target location should be able to include the usual vars that eclipse offers in launches and elsewhere.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
