Eclipse Community Forums: P2 dev » Virgo build p2 sanity check

Help

Home

Home » Archived » P2 dev » Virgo build p2 sanity check

Show: Today's Messages :: Show Polls :: Message Navigator

Virgo build p2 sanity check [message #538699]

Tue, 08 June 2010 12:53

Glyn Normington

Messages: 1222
Registered: July 2009

Senior Member

I would be grateful for a sanity check of how we are thinking of using p2 while building the Eclipse Virgo project.

Virgo is split into a number of components each of which has a git repository and a Hudson build. The components depend on each other, with the dependencies forming a DAG.

When we successfully build a snapshot of a component, we want to make the bundles of the snapshot available for builds of other components to consume. We have been advised to use p2.

So we are thinking of making each snapshot build construct a p2 repository of built bundles in the build's workspace and, if the build is successful, to promote the contents of the workspace p2 repository to a common Virgo p2 repository in the Virgo downloads area.

The benefit of publishing to a common repository is that component builds need only specify the location of the common repository rather than having to construct some kind of search sequence of all the repositories of components containing dependencies.

Thoughts?

Report message to a moderator

Re: Virgo build p2 sanity check [message #539493 is a reply to message #538699]

Fri, 11 June 2010 01:38

Pascal Rapicault

Messages: 333
Registered: July 2009
Location: Ottawa

Senior Member

I can't really think of any issue with this at this point. Internally at sonatype, we have been using something similar approaches to build our osgi based products.

Report message to a moderator

Previous Topic:	update one feature separately from RCP shell, how?
Next Topic:	Forum existence

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Apr 18 23:11:51 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter