|Re: Multiphase creation of update site? [message #611621]
||Wed, 01 September 2010 06:23
Originally posted by: dhendriksREMOVE_THIS.tueREMOVE.THIS.nl|
After being redirected to b3 from Buckminster, my question is whether
the scenario I presented (see below) is supported by b3. That is, does
(or will) b3 support automation of multi-phase build processes?
If so, what is the status of the implementation; is it ready for use in
real-life projects (as I read that b3 is still in the proposal phase:
Henrik Lindberg wrote:
> this is one of the goals of Eclipse b3 as it has a lot more
> compositional flexibility, and has unified all of the artifacts used by
> Buckminster into one.
> Don't think this will be supported directly in Buckminster even when
> used as an engine behind the scenes.
> - henrik
> On 7/16/10 3:18 PM, Dennis Hendriks wrote:
>> For my QVTo project, I would like to create a p2 update site. The QVTo
>> file cannot be parsed if I don't have the metamodel it depends on
>> installed. Also, it requires a blackbox library, provided by an other
>> Java plug-in. Note that it is not enough to have the projects in the
>> workspace, I actually need the distributed jars installed into headless
>> What I do now, is create an update site for the metamodel/EMF project,
>> and the blackbox library Java plug-in project. Then install those
>> plug-ins into headless Buckminster. Then I create an update site for the
>> QVTo project, together with the other two projects.
>> This requires multiple phases, and multiple intermediate/temporary
>> update sites. I needed to create a shell script and invoke Buckminster
>> with various commands, and different rmaps/cqueries for the multiple
>> phases. Is there any way to avoid this, that is, to automatically have
>> this resolved etc? I think it would be within the goal of Buckminster to
>> automatically do this for me, right?
Powered by FUDForum
. Page generated in 0.02099 seconds