[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [p2-dev] I surrender


I tried several times to use the InstallPublisher to no avail. Unfortunately, I could only guess at the required params. The only place that seemed to mention it didn't provide details like the other publishers:



-----Original Message-----
From: Pascal Rapicault <pascal@xxxxxxxxxxxxx>
To: P2 developer discussions <p2-dev@xxxxxxxxxxx>
Sent: Thu, Apr 26, 2012 11:00 am
Subject: Re: [p2-dev] I surrender


p2 expects the application you are installing into to have been p2-enabled. This 
means that the basic Eclipse install you have and in which you are installing 
should have a p2 folder in its root. You get to that state by installing this 
base with p2 itself.
To be able to install something with p2 you need to have p2 metadata for it. So 
the first problem is to generate p2 metadata for the complete installation.
There are two ways to get to that:
- Use PDE Build or Tycho to build the product and get them to generate complete 
metadata for the product and produce the p2 enabled product. This is the 
recommended way (this is for ppl running into this post without the complete 
- Generate metadata on the result of your own build using the 
org.eclipse.equinox.p2.publisher.InstallPublisher. This application takes as 
input an eclipse install and generate p2 metadata and artifact from it. With the 
repositories produced by this application you can then use the p2 director to 
get the p2 enabled application.

Should you care about the p2 folder?
No. The p2 folder is not something that you have to edit. It is p2 internal 
representation of what it knows about the system being managed.

Are you trying to figure this out from a selfhosted environment? The support for 
running p2 in a selfhosted environment is not ideal and this may be one of the 


Training, consulting, bug fixing - pascal at rapicault dot net