|Re: TeamProjectSet repository-folder [message #1507201 is a reply to message #1504904]
||Thu, 11 December 2014 12:00
| Ed Merks
Registered: July 2009
Most often team project set files are a poor-mans solution for trying to
automate workspace provisioning. Oomph provides richer mechanisms for
For example, Oomph supports a Git clone task you can can decide where
you want your close to be; with team project sets you have no real
control over that. Once you have a clone, something like a Targlet task
is very useful, assuming your projects are actually plug-ins and
features. With a targlet task you can provision the workspace and
target platform simultaneously. If your projects can't plugins and
features, you can use the Projects Import task to import them into the
workspace (without ensure their dependencies are satisfied by the target
With this approach you can configure everything, and avoid these rather
crappy team project set files...
If you have questions about Oomph, you can ask on the eclipse.oomph forum.
On 09/12/2014 6:19 PM, kurt Mising name wrote:
> As far as I understood the EGit-documentation, the git-repositories
> should not be located in the workspace-folder.
> But importing projects via TeamProjectSets does exactly that.
> At least EGit 3.4.1 does so.
> Shouldn't it honor the EGit-configuration ("Default repository folder") ?
> Even nicer would be, if there was an API to set the repository-folder.
Powered by FUDForum
. Page generated in 0.01981 seconds