Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
maven-bundle-plugin-4.1.0
-
None
-
None
-
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T20:41:47+02:00)
Maven home: C:\Program Files\Java\maven\bin\..
Java version: 11.0.1, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk\default
Default locale: en_US, platform encoding: Cp1250
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T20:41:47+02:00) Maven home: C:\Program Files\Java\maven\bin\.. Java version: 11.0.1, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk\default Default locale: en_US, platform encoding: Cp1250 OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Description
Dependencies on OSGi-fied JPMS modules produce warnings about split packages. Even using the suggested -split-package directive does not make the warning disappear (anyway, it should not appear in the first place as there is no reason for it).
The interesting point is that when module-info is absent in the dependency, the warning does not appear at all.
A small project that demonstrates the behavior is attached.
I personally consider this bug very annoying as seems to hurt any attempts for dual JPMS/OSGi libraries.