Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.4, 2.5
-
None
-
None
-
None
Description
In 2.4 you added
<commons.osgi.export> <!-- Explicit list of packages from IO 1.4 --> org.apache.commons.io; org.apache.commons.io.comparator; org.apache.commons.io.filefilter; org.apache.commons.io.input; org.apache.commons.io.output;version=1.4.9999;-noimport:=true, <!-- Same list plus * for new packages --> org.apache.commons.io; org.apache.commons.io.comparator; org.apache.commons.io.filefilter; org.apache.commons.io.input; org.apache.commons.io.output; org.apache.commons.io.*;version=${project.version};-noimport:=true </commons.osgi.export>
This creates an entry in the MANIFEST.MF like
Import-Package: org.apache.commons.io;version="[1.4,2)"
Which leads to our bundles not working with 2.4, as we are exporting 2.4 and not 1.4 in our application.
I think the solution is, that if somebody want's to use it as 1.4 he should export the packages as 1.4 by themselves.
I added an example project.
Attachments
Attachments
Issue Links
- is broken by
-
IO-333 Export OSGi packages at version 1.x in addition to 2.x
- Closed