| any way to have the batch build generate the p2 descriptor files? [message #1205] |
Thu, 17 April 2008 10:58  |
Eclipse User |
|
|
|
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
|
|
|
| [p2] Re: any way to have the batch build generate the p2 descriptor files? [message #1232 is a reply to message #1205] |
Thu, 17 April 2008 15: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
|
|
|
| [p2] Re: any way to have the batch build generate the p2 descriptor files? [message #565790 is a reply to message #1205] |
Thu, 17 April 2008 15:14 |
| Eclipse User |
|
|
|
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
|
|
|
Powered by
FUDForum. Page generated in 0.03228 seconds
Home