[IO-734] The OSGi manifest now contains sun.* packages in the Import-Package instruction

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9.0
• Fix Version/s: 2.10.0
• Assignee: Unassigned
• Reporter: Eric Norman
• Created: 30/May/21 19:16
• Updated: 07/Jun/21 13:02
• Resolved: 31/May/21 20:19

Description

After attempting to upgrade to commons-io:2.9.0 for apache sling I see that there are now required imports for some sun.* packages in the OSGi manifest.  These references appear to be coming from a new BufferedFileChannelInputStream class in version 2.9.0.

This results in an error for OSGi environments where those packages are not exposed anywhere.

Specifically this error:

 

commons-io:commons-io:2.9.0: is importing package(s) [sun.nio.ch, sun.misc] in start level 5 but no bundle is exporting these for that start level. 

It would be best if commons-io was not using sun.* packages, but if you must reference those then perhaps those imported packages could be marked optional in the manifest so the commons-io OSGi bundle will not fail to activate when those are not available?

Issue Links

• is duplicated by: IO-738 com.sun.nio should be an optional import
• is duplicated by: IO-735 2.9.0 breaks OSGi with new Import-Package header
• links to: PR #239