Sebastien ARBOGAST wrote:
It's weird because after using Private-Package, my manifest looks like this:
Export-Package: com.mycompany.myapp.impl;uses:="com.mycompany.myapp",
com.mycompany.myapp
Private-Package: com.mycompany.myapp.impl
Is it normal that impl is still in Export-Package?
Did you cut and paste that directly? Because it doesn't look correct.
Private packages are not exported. Perhaps there is some mistake in your
POM?
-> richard
2008/3/29, Richard S. Hall <[EMAIL PROTECTED]>:
Sebastien ARBOGAST wrote:
I have a bundle with some service interfaces in com.mycompany.myapp and
their implementations in com.mycompany.myapp.implSince I only want to
export
interfaces and not implementations, I add the following directive to
maven-bundle-plugin configuration:
<Export-Package>com.mycompany.myapp</Export-Package>
But then the problem is that implementations are not in the resulting
bundle. And if I a "*" to the package, implementation classes are in the
bundle but the impl package is exported in the manifest.
How is it that the Export-Package directive also controls which classes
are
bundled?
FYI I'm using version 1.4.0 of maven-bundle-plugin.
You need to use
<Private-Package>com.mycompany.myapp.impl</Private-Package> to include
packages that are not exported.
-> richard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
