|
| Re: How to ship PDE/P2 build product with update sites pre-configured [message #605848 is a reply to message #605787] |
Tue, 25 May 2010 14:51  |
 Andrew Niefer
Messages: 990
Registered: July 2009 |
Senior Member |
|
|
Since you are using "p2.gathering=true", you can provide a p2.inf file
beside your .product file.
http://wiki.eclipse.org/Equinox/p2/Customizing_Metadata
Add something like the following:
instructions.configure.import= \
org.eclipse.equinox.p2.touchpoint.eclipse.addRepository
instructions.configure=\
addRepository(type:0,location:http${#58}//example.com/reposi tory,\
name:My Repository);\
addRepository(type:1,loation:http${#58}//example.com/reposit ory,\
name:My Repository);
0) The import isn't strictly necessary for p2.inf beside the .product file,
but will be necessary if you put it beside a feature.xml instead.
1) this is a java Properties file, I just escaped the newlines with \
to make it more readable
2) You need the repository twice, the 'type' is metadata or artifact
3) Notice the escaping of the colon with ${#58}
-Andrew
Eddie Galvez wrote:
> We build a product using PDE headless build, enabling P2
> (p2.gathering=true), but when the product is run and one goes to install
> new software, no update sites are preconfigured.
>
> I tried adding update sites ("discovery") to our main feature's manifest,
> and that had no effect.
>
> I'm just trying to place the eclipse 3.5 update sites (galileo and
> platform project updates) into our product, that's all.
|
|
|
Powered by
FUDForum. Page generated in 0.02780 seconds
] 
Search
Help
Register
Login
Home
