On 10 December 2010 16:44, Rice Yeh <[email protected]> wrote:
> No, it still does not work.
>
The following configuration doesn't export the "org.foo.sh" package, as
expected:
<build>
<plugins>
<plugin>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>2.1.0</version>
<extensions>true</extensions>
<configuration>
<instructions>
<Export-Package/>
<Private-Package>org.foo.sh</Private-Package>
</instructions>
</configuration>
</plugin>
</plugins>
</build>
what configuration are you using in your POM?
--
Cheers, Stuart
> On Fri, Dec 10, 2010 at 9:58 PM, Richard S. Hall <[email protected]
> >wrote:
>
> > Seems like what you have should work. Maybe try something like:
> >
> > <Export-Package>!org.foo.sh</Export-Package>
> >
> > But still sounds odd to me.
> >
> > -> richard
> >
> >
> > On 12/10/10 3:46, Rice Yeh wrote:
> >
> >> Hi,
> >> My bundle has only one package org.foo.sh, but I do not like to
> export
> >> it. How do I do it with BND instructions thru. maven-bundle-plugin. My
> >> current instructions have no Export-Package and have org.foo.shincluded
> >> in
> >> Private-Package as shown below. But I still get a manifest with
> >> org.foo.shlisted in Export-Package.
> >>
> >>
> >> <Export-Package></Export-Package>
> >> <Private-Package>org.foo.sh</Private-Package>
> >>
> >>
> >> Regards,
> >> Rice
> >>
> >>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>
