[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] Using one agent to install a different product

Pascal, Terry (and others)

I think i have tracked some stuff down regarding this.

running ./eclipse -application  org.eclipse.equinox.p2.director.app.application -metadataRepo .. -artifactRepo .... -vmArgs -Declipse.p2.data.area=/some/new/dir

If I put a breakpoint in loadRepository, I get a whole bunch of repos added, including:
Other ones used in previous runs of the director

However, p2 data area is a completely new directory (nothing there).  So, I'm not sure if the director should be loading other repositories.  I think this explains why p2 is finding bits I didn't expect it too.  

does anyone have thoughts on this?  Should repos be stored in the p2 data area, and a clean area start with no known repos?


On Tue, Mar 3, 2009 at 5:07 PM, Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx> wrote:

> I was wondering if this is an acceptable use of the director.
> 1. D/L eclipse 3.5 (Say M5)
> 2. Create a 3.4.1 repo
> Use the director in eclipse 3.5 (./eclipse -application ..director..
> ) and point it to my eclipse 3.4.1 install and install something.

Do you mean point at my 3.4.1 repo?

> I realize that metadata may not be compatible, but that it not the
> problem I'm experiencing.  Essentially, when I do this, I get a
> bunch of errors around IUs with version numbers like 3.5.0
> (200902..).  So even though I pointed it at a 3.4.1 repo (and
> pointed my p2 data area to a clean dir), bundles from 3.5 are being
> found (and provisioned).  

This is rather weird and is expected to work since this resemble the p2 usage of the automated build.
Make sure you specify the correct arguments on your application: http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.platform.doc.isv/guide/p2_director.html
You may also be encountering https://bugs.eclipse.org/bugs/show_bug.cgi?id=251622


p2-dev mailing list

R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource