Eclipse Community Forums: Buckminster » finding out dependencies when building a product

Home » Archived » Buckminster » finding out dependencies when building a product

finding out dependencies when building a product [message #532213]

Fri, 07 May 2010 10:34

Eclipse User

I'm trying to build a product out of our toolchain and debugger plugins,
so that we can deliver a branded IDE. To include the relevant parts of
the Eclipse workbench we need I have a "platform"-feature which includes
all the plugins we need to include.

The problem is how to figure out which plugins we need to include.
Currently I'm adding plugins one at a time and then creating the product
to see what the director application complains about. Lather, rinse, repeat.

Although this seems to work, isn't there an easier way to do this?

--
/Jesper

Re: finding out dependencies when building a product [message #532220 is a reply to message #532213]

Fri, 07 May 2010 10:52

Eclipse User

Hi Jesper,

you can do the following:
1. create a target platform definition to compile against (that's
usually a good idea), but don't include anything from your local
installation, but use for example a number of update sites.
2. create a feature that contains your stuff
3. for the headless build start by activating the target platform defintion
4. resolve your query
5. build a p2 site from your feature
6. invoke the create product action

In the ant file that starts the p2 director you can specify a list of
update sites and a list of IUs, not just one. For the repositories you
add the output of the site.p2 action (e.g. ${sp:repository}) and all
other repositories that you used in your target definition file.
As IUs you pass the product/feature you built as well as any additional
IUs that you want in your final product.
The p2 director will then install all listed IUs and resolves
dependencies against all listed repositories.

In production environments it makes sense of course to mirror all
external update sites in the intranet to not depend on external
resources. The b3 aggregator (former Buckminster Aggregator) is just
great for this task.

Hope that helps and best regards,
Johannes

Re: finding out dependencies when building a product [message #532231 is a reply to message #532220]

Fri, 07 May 2010 11:27

Eclipse User

On 2010-05-07 16:52, Johannes Utzig wrote:
> Hi Jesper,
>
> you can do the following:
> 1. create a target platform definition to compile against (that's
> usually a good idea), but don't include anything from your local
> installation, but use for example a number of update sites.
> 2. create a feature that contains your stuff
> 3. for the headless build start by activating the target platform defintion
> 4. resolve your query
> 5. build a p2 site from your feature
> 6. invoke the create product action

Yes, this is more or less how I am doing it now.

> In the ant file that starts the p2 director you can specify a list of
> update sites and a list of IUs, not just one. For the repositories you
> add the output of the site.p2 action (e.g. ${sp:repository}) and all
> other repositories that you used in your target definition file.
> As IUs you pass the product/feature you built as well as any additional
> IUs that you want in your final product.
> The p2 director will then install all listed IUs and resolves
> dependencies against all listed repositories.

Ok. This sounds like a more sane method.

> In production environments it makes sense of course to mirror all
> external update sites in the intranet to not depend on external
> resources. The b3 aggregator (former Buckminster Aggregator) is just
> great for this task.

Yes, this is on my todo-list already. :-)

> Hope that helps and best regards,
> Johannes

Thanks a lot!

--
/Jesper

Re: finding out dependencies when building a product [message #532246 is a reply to message #532220]

Fri, 07 May 2010 12:31

Eclipse User

On 2010-05-07 16:52, Johannes Utzig wrote:
> Hi Jesper,
>
> you can do the following:
> 1. create a target platform definition to compile against (that's
> usually a good idea), but don't include anything from your local
> installation, but use for example a number of update sites.
> 2. create a feature that contains your stuff
> 3. for the headless build start by activating the target platform defintion
> 4. resolve your query
> 5. build a p2 site from your feature
> 6. invoke the create product action
>
> In the ant file that starts the p2 director you can specify a list of
> update sites and a list of IUs, not just one. For the repositories you
> add the output of the site.p2 action (e.g. ${sp:repository}) and all
> other repositories that you used in your target definition file.
> As IUs you pass the product/feature you built as well as any additional
> IUs that you want in your final product.
> The p2 director will then install all listed IUs and resolves
> dependencies against all listed repositories.

How do I specify a list of update sites and a list of IUs? Do I pass
multiple -artifactRepository/-metadataRepository/-installIU options to
the director application?

--
/Jesper

Re: finding out dependencies when building a product [message #532327 is a reply to message #532246]

Sat, 08 May 2010 03:13

Eclipse User

On 05/07/2010 06:31 PM, Jesper Eskilson wrote:
> How do I specify a list of update sites and a list of IUs? Do I pass
> multiple -artifactRepository/-metadataRepository/-installIU options to
> the director application?
>
Yes. You can pass either a comma separated list, or repeat the options.

- thomas

Previous Topic:	site.p2.zip action does not produce zipped site in Hudson
Next Topic:	b3 aggregator problem

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jul 07 13:33:57 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter