Home » Eclipse Projects » Plugin Development Environment (PDE) » PDE Build, p2 & bundles.info
| PDE Build, p2 & bundles.info [message #66516] |
Thu, 02 July 2009 11:31  |
Eclipse User |
|
|
|
I am trying to automate the build, using pde build, of a p2-enabled, 3.4
version of Simon's servletbridge.
By manual assembly and configuration I have a working version of the
servletbridge using 3.4 bundles and p2-enbaled. Using the osgi console api
I can provision new bundles into the system using p2. This is excellent.
But I know need to automate the build of this product.
To some extent I've been able to do this. I have a build script that uses
pde build to build a root feature, p2 generator to generate p2 metadata and
artifact repositories and p2 director to install the root feature into my
webapp structure. This also generates the p2 profile.
What I dont know is how to deal with the bundles.info file.
Is the p2 director app meant to generate it for me?
How do you manage this yourselves for the various eclipse products that you
now build; j2ee, classic, etc?
Thanks in advance
_Paul
|
|
|
| Re: PDE Build, p2 & bundles.info [message #67387 is a reply to message #66516] |
Mon, 06 July 2009 17:50  |
| Eclipse User |
|
|
|
The director app will generate the bundles.info for you, but only if you
include org.eclipse.equinox.simpleconfigurator, and you have metadata
that starts that bundle.
To get the appropriate start level metadata generated, you should look
at doing a product build. (You can define "includeLaunchers=false" to
get a product build without launchers).
I believe the 3.5 versions of the various eclipse packages are built
from .product files.
Paul Warren wrote:
> I am trying to automate the build, using pde build, of a p2-enabled, 3.4
> version of Simon's servletbridge.
>
> By manual assembly and configuration I have a working version of the
> servletbridge using 3.4 bundles and p2-enbaled. Using the osgi console api
> I can provision new bundles into the system using p2. This is excellent.
>
> But I know need to automate the build of this product.
>
> To some extent I've been able to do this. I have a build script that uses
> pde build to build a root feature, p2 generator to generate p2 metadata and
> artifact repositories and p2 director to install the root feature into my
> webapp structure. This also generates the p2 profile.
>
> What I dont know is how to deal with the bundles.info file.
>
> Is the p2 director app meant to generate it for me?
>
> How do you manage this yourselves for the various eclipse products that you
> now build; j2ee, classic, etc?
>
> Thanks in advance
> _Paul
>
>
|
|
|
| Re: PDE Build, p2 & bundles.info [message #67534 is a reply to message #67387] |
Wed, 08 July 2009 06:53 |
| Eclipse User |
|
|
|
Hi Andrew,
That worked for me. Many thanks.
Is there anyway that I can influence the startlevel and activate flag that
each bundle entry gets in the bundles.info file?
Thanks,
_Paul
"Andrew Niefer" <aniefer@ca.ibm.com> wrote in message
news:h2trig$s66$1@build.eclipse.org...
> The director app will generate the bundles.info for you, but only if you
> include org.eclipse.equinox.simpleconfigurator, and you have metadata that
> starts that bundle.
>
> To get the appropriate start level metadata generated, you should look at
> doing a product build. (You can define "includeLaunchers=false" to get a
> product build without launchers).
>
> I believe the 3.5 versions of the various eclipse packages are built from
> .product files.
>
>
> Paul Warren wrote:
>> I am trying to automate the build, using pde build, of a p2-enabled, 3.4
>> version of Simon's servletbridge.
>>
>> By manual assembly and configuration I have a working version of the
>> servletbridge using 3.4 bundles and p2-enbaled. Using the osgi console
>> api I can provision new bundles into the system using p2. This is
>> excellent.
>>
>> But I know need to automate the build of this product.
>>
>> To some extent I've been able to do this. I have a build script that
>> uses pde build to build a root feature, p2 generator to generate p2
>> metadata and artifact repositories and p2 director to install the root
>> feature into my webapp structure. This also generates the p2 profile.
>>
>> What I dont know is how to deal with the bundles.info file.
>>
>> Is the p2 director app meant to generate it for me?
>>
>> How do you manage this yourselves for the various eclipse products that
>> you now build; j2ee, classic, etc?
>>
>> Thanks in advance
>> _Paul
>>
|
|
|
| Re: PDE Build, p2 & bundles.info [message #599064 is a reply to message #66516] |
Mon, 06 July 2009 17:50 |
| Eclipse User |
|
|
|
The director app will generate the bundles.info for you, but only if you
include org.eclipse.equinox.simpleconfigurator, and you have metadata
that starts that bundle.
To get the appropriate start level metadata generated, you should look
at doing a product build. (You can define "includeLaunchers=false" to
get a product build without launchers).
I believe the 3.5 versions of the various eclipse packages are built
from .product files.
Paul Warren wrote:
> I am trying to automate the build, using pde build, of a p2-enabled, 3.4
> version of Simon's servletbridge.
>
> By manual assembly and configuration I have a working version of the
> servletbridge using 3.4 bundles and p2-enbaled. Using the osgi console api
> I can provision new bundles into the system using p2. This is excellent.
>
> But I know need to automate the build of this product.
>
> To some extent I've been able to do this. I have a build script that uses
> pde build to build a root feature, p2 generator to generate p2 metadata and
> artifact repositories and p2 director to install the root feature into my
> webapp structure. This also generates the p2 profile.
>
> What I dont know is how to deal with the bundles.info file.
>
> Is the p2 director app meant to generate it for me?
>
> How do you manage this yourselves for the various eclipse products that you
> now build; j2ee, classic, etc?
>
> Thanks in advance
> _Paul
>
>
|
|
|
| Re: PDE Build, p2 & bundles.info [message #599119 is a reply to message #67387] |
Wed, 08 July 2009 06:53 |
| Eclipse User |
|
|
|
Hi Andrew,
That worked for me. Many thanks.
Is there anyway that I can influence the startlevel and activate flag that
each bundle entry gets in the bundles.info file?
Thanks,
_Paul
"Andrew Niefer" <aniefer@ca.ibm.com> wrote in message
news:h2trig$s66$1@build.eclipse.org...
> The director app will generate the bundles.info for you, but only if you
> include org.eclipse.equinox.simpleconfigurator, and you have metadata that
> starts that bundle.
>
> To get the appropriate start level metadata generated, you should look at
> doing a product build. (You can define "includeLaunchers=false" to get a
> product build without launchers).
>
> I believe the 3.5 versions of the various eclipse packages are built from
> .product files.
>
>
> Paul Warren wrote:
>> I am trying to automate the build, using pde build, of a p2-enabled, 3.4
>> version of Simon's servletbridge.
>>
>> By manual assembly and configuration I have a working version of the
>> servletbridge using 3.4 bundles and p2-enbaled. Using the osgi console
>> api I can provision new bundles into the system using p2. This is
>> excellent.
>>
>> But I know need to automate the build of this product.
>>
>> To some extent I've been able to do this. I have a build script that
>> uses pde build to build a root feature, p2 generator to generate p2
>> metadata and artifact repositories and p2 director to install the root
>> feature into my webapp structure. This also generates the p2 profile.
>>
>> What I dont know is how to deal with the bundles.info file.
>>
>> Is the p2 director app meant to generate it for me?
>>
>> How do you manage this yourselves for the various eclipse products that
>> you now build; j2ee, classic, etc?
>>
>> Thanks in advance
>> _Paul
>>
|
|
|
Goto Forum:
Current Time: Sat May 31 18:46:17 EDT 2025
Powered by FUDForum. Page generated in 0.23692 seconds |
Home