[
https://issues.apache.org/jira/browse/FELIX-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681213#action_12681213
]
Stuart McCulloch commented on FELIX-981:
----------------------------------------
FYI, this only appears to occur when a package appears in both Private-Package
and Export-Package and the directive appears on one but not the other. While
BND will favour Export-Package over Private-Package and export it, it appears
the split package check is performed twice for each instruction hence the
warning. Previously the bundleplugin default for Private-Package often didn't
match the packages in the bundle, which would explain why you see this in 2.0.0
but not 1.4.3, because in 1.4.3 the foo package wouldn't be in the default
Private-Package whereas in 2.0.0 it will be (without the split-package
directive).
There are several ways we can fix this - either by adjusting the default
private packages in the bundleplugin, or by only checking once in the bndlib
code.
Until then you can safely ignore this warning, because the actual generation of
the bundle is still the same.
> Warning about split packages even with -split-package directive
> [maven-bundle-plugin-2.0.0]
> -------------------------------------------------------------------------------------------
>
> Key: FELIX-981
> URL: https://issues.apache.org/jira/browse/FELIX-981
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.0.0
> Environment: Maven version: 2.0.9
> Java version: 1.6.0_12
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Clovis Seragiotto
> Priority: Minor
> Fix For: maven-bundle-plugin-2.0.1
>
> Attachments: split-packages.zip
>
>
> A warning about split packages is issued even if you use -split-package in
> your Export-Package instruction.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
