| [p2] Re: any way to have the batch build generate the p2 descriptor files? [message #108363] |
Thu, 17 April 2008 19:14  |
Eclipse User |
|
|
|
Originally posted by: zx.us.ibm.com
This question is better for the Equinox newsgroup.
Francis Upton wrote:
> Sorry for not looking at the code and trying to figure this out myself,
> but I thought maybe someone would have a quick answer.
>
> I use the PDE build scripts and have not changed them for 3.4, I notice
> that in my generated products there is nothing p2 related. The
> generated apps work just fine.
>
> However, I want to actually generate the p2 file that says what's to be
> used, because for one of my products I want to withhold a plugin
> (because that plugin will be in the application's class path in order
> for me to expose it as an API to the application). (I also need to
> figure out a way to tell p2 which of these p2 files to use on startup --
> I'm using EclipseStarter, so I assume there is some property that I can
> set for this).
>
> Can the automated build generate this file somehow? Or is there a
> better way to solve this problem short of creating an entirely separate
> product with it's own copy of everything?
>
> Thanks,
>
> Francis
|
|
|
| Re: [p2] Re: any way to have the batch build generate the p2 descriptor files? [message #108413 is a reply to message #108363] |
Mon, 21 April 2008 10:31  |
 Francis Upton IV
Messages: 472
Registered: July 2009
Location: Oakland, CA |
Senior Member |
|
|
Well I figured out how to teach the headless build how to do to this,
and then realized the approach was completely wrong. The bundles.info
file really needs to be generated in-sutu at the first startup because
it actually has the paths to the bundles, so it's not something that can
be done at generation time.
I imagine that I could use some kind of more sophisticated p2
configurator to be able to withhold a bundle given a particular
execution, but I think I will hold off on this for the time being until
p2 gets further along.
In the meantime I will just create a different product (and thus
installation) for the case where I need to have the one plugin withheld.
Unless someone has a better idea.
Francis
Chris Aniszczyk wrote:
> This question is better for the Equinox newsgroup.
>
> Francis Upton wrote:
>> Sorry for not looking at the code and trying to figure this out
>> myself, but I thought maybe someone would have a quick answer.
>>
>> I use the PDE build scripts and have not changed them for 3.4, I
>> notice that in my generated products there is nothing p2 related. The
>> generated apps work just fine.
>>
>> However, I want to actually generate the p2 file that says what's to
>> be used, because for one of my products I want to withhold a plugin
>> (because that plugin will be in the application's class path in order
>> for me to expose it as an API to the application). (I also need to
>> figure out a way to tell p2 which of these p2 files to use on startup
>> -- I'm using EclipseStarter, so I assume there is some property that I
>> can set for this).
>>
>> Can the automated build generate this file somehow? Or is there a
>> better way to solve this problem short of creating an entirely
>> separate product with it's own copy of everything?
>>
>> Thanks,
>>
>> Francis
Platform UI Committer for Common Navigator
http://wiki.eclipse.org/index.php/Common_Navigator_Framework
http://help.eclipse.org/galileo/topic/org.eclipse.platform.d oc.isv/guide/cnf.htm
|
|
|
|
Powered by
FUDForum. Page generated in 0.02942 seconds
] 
Search
Help
Register
Login
Home
