|Re: reusing setups/tasks [message #1386034 is a reply to message #1385974]
||Fri, 13 June 2014 06:53
| Ed Merks
Registered: July 2009
On 12/06/2014 4:31 PM, Alexander Nittka wrote:
> is there a recommended way for reusing/aggregating setups, tasks, etc.
The only mechanism is subproject nesting..
> The simple scenario would be as follows. You want to keep p2-tasks and
You mean variables?
> for various features in separate models, e.g. p2-task for the Xtext
> update site, plugins as well as builder and highlighting properties in
Sounds like preferences then?
> checkstyle plugins and properties in Y.setup.
Certainly with regard to p2 task, it's just an issue of the IU being
specified and the p2 site to get it from. The p2 site could be shared
up in a root project and in a subproject you could specify to actually
install an IU from it, i.e., p2 tasks typically merge into a single task
for the stream in the leaf project.
> For project P1 you only need Xtext, so you would want to include
> X.setup in its project description, for project P2 you need Xtext as
> well as checkstyle sou you would want to include X.setup and Y.setup.
So you could nest all the projects that need checkstyle under a project
that specifies the checkstyle stuff. Only projects with streams can
actually be directly provisioned, so the container projects are just
places to keep common tasks.
Powered by FUDForum
. Page generated in 0.03006 seconds