You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Stuart McCulloch <st...@jayway.net> on 2008/02/01 18:41:46 UTC
bundleplugin 1.2.1-SNAPSHOT
Hi folks,
I've deployed a new 1.2.1-SNAPSHOT of the bundleplugin with Peter's improved
"uses:" support...
1) generated "uses:" clause no longer include implementation packages
2) you can now turn off all the generated "uses:" clause with:
<_nouses>true</_nouses>
( or -nouses: true if you use a Bnd properties file )
3) or you can add your own customized "uses:" clause to your
Export-Package:
com.acme.impl.*;uses="my.special.import"
as well as mix customized and generated "uses:" like so:
com.acme.impl.*;uses="my.special.import,<<USES>>"
Enjoy :)
--
Cheers, Stuart
Re: bundleplugin 1.2.1-SNAPSHOT
Posted by Stuart McCulloch <st...@jayway.net>.
On 02/02/2008, Niall Pemberton <ni...@gmail.com> wrote:
>
> On Feb 1, 2008 5:41 PM, Stuart McCulloch <st...@jayway.net>
> wrote:
> > Hi folks,
> >
> > I've deployed a new 1.2.1-SNAPSHOT of the bundleplugin with Peter's
> improved
> > "uses:" support...
> >
> > 1) generated "uses:" clause no longer include implementation packages
>
> Maybe I'm doing something wrong - but the uses are still there but the
> version number no longer is.
Correct - by default the "uses:" clause will still be there, except it now
won't
include any private packages (ie. packages that aren't imported or exported)
which it did previously. What's left are the correct set of used packages.
To remove the "uses:" clause completely you need to set -nouses to true:
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>1.2.1-SNAPSHOT</version>
<configuration>
<instructions>
<_nouses>true</_nouses>
<!-- etc. -->
</instructions>
</configuration>
</plugin>
Regarding the missing version, I've just fixed that - it only occurs when
you
don't set Private-Package (I moved some setup code so it would also work
with included files, and it needs an additional check to stop it altering
the
exports that were just loaded).
I've deployed a new snapshot (1.2.1-20080202.145318-5) with this fix.
Niall
>
> > 2) you can now turn off all the generated "uses:" clause with:
> >
> > <_nouses>true</_nouses>
> >
> > ( or -nouses: true if you use a Bnd properties file )
> >
> > 3) or you can add your own customized "uses:" clause to your
> > Export-Package:
> >
> > com.acme.impl.*;uses="my.special.import"
> >
> > as well as mix customized and generated "uses:" like so:
> >
> > com.acme.impl.*;uses="my.special.import,<<USES>>"
> >
> > Enjoy :)
> >
> > --
> > Cheers, Stuart
> >
>
--
Cheers, Stuart
Re: bundleplugin 1.2.1-SNAPSHOT
Posted by Niall Pemberton <ni...@gmail.com>.
On Feb 1, 2008 5:41 PM, Stuart McCulloch <st...@jayway.net> wrote:
> Hi folks,
>
> I've deployed a new 1.2.1-SNAPSHOT of the bundleplugin with Peter's improved
> "uses:" support...
>
> 1) generated "uses:" clause no longer include implementation packages
Maybe I'm doing something wrong - but the uses are still there but the
version number no longer is.
Niall
> 2) you can now turn off all the generated "uses:" clause with:
>
> <_nouses>true</_nouses>
>
> ( or -nouses: true if you use a Bnd properties file )
>
> 3) or you can add your own customized "uses:" clause to your
> Export-Package:
>
> com.acme.impl.*;uses="my.special.import"
>
> as well as mix customized and generated "uses:" like so:
>
> com.acme.impl.*;uses="my.special.import,<<USES>>"
>
> Enjoy :)
>
> --
> Cheers, Stuart
>
Re: bundleplugin 1.2.1-SNAPSHOT
Posted by Alin Dreghiciu <ad...@gmail.com>.
bnd 0.0.236 form 1.2.1-SNAPSHOT also solves the following:
It was tricky! It turned out that the inline copied also the manifest.
When calculating the manifest, bnd thought that this was the original
manifest of a wrapped bundle. The solution is now to not copy the
manifest for an inline.
Version 0.0.236 solves your problem ... sorry for the delay ...
Kind regards,
Peter Kriens
On 24 jan 2008, at 11:01, Alin Dreghiciu wrote:
> Hi Peter,
>
> I found the following case:
> 1. I have a bundle that inlines another bundle jar
> 2. The inlined bundle has an osgi manifest header (e.g. Export-
> Package: xxx)
> 3. The bundle (from 1) does not use that header, for example it does
> not Export any package)
>
> In this case the generated manifest of the bundle (1) will contain the
> export-Package: xxx from inlined bundle. fact that is not what I want.
> In my view if you inline another bundle bnd should not keep any of the
> osgi specific headers.
On Feb 2, 2008 1:41 AM, Stuart McCulloch <st...@jayway.net> wrote:
> Hi folks,
>
> I've deployed a new 1.2.1-SNAPSHOT of the bundleplugin with Peter's improved
> "uses:" support...
>
> 1) generated "uses:" clause no longer include implementation packages
>
> 2) you can now turn off all the generated "uses:" clause with:
>
> <_nouses>true</_nouses>
>
> ( or -nouses: true if you use a Bnd properties file )
>
> 3) or you can add your own customized "uses:" clause to your
> Export-Package:
>
> com.acme.impl.*;uses="my.special.import"
>
> as well as mix customized and generated "uses:" like so:
>
> com.acme.impl.*;uses="my.special.import,<<USES>>"
>
> Enjoy :)
>
> --
> Cheers, Stuart
>