commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Moerchen (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IO-350) Maven-Bundle-Plugin imports version 2.4 as 1.4
Date Tue, 23 Oct 2012 07:27:13 GMT
Adrian Moerchen created IO-350:
----------------------------------

             Summary: Maven-Bundle-Plugin imports version 2.4 as 1.4
                 Key: IO-350
                 URL: https://issues.apache.org/jira/browse/IO-350
             Project: Commons IO
          Issue Type: Bug
    Affects Versions: 2.4
            Reporter: Adrian Moerchen
         Attachments: commons-io-osgi-bug.zip

In 2.4 you added 
{code}
 <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>
{code}

This creates an entry in the MANIFEST.MF like
{code}
Import-Package: org.apache.commons.io;version="[1.4,2)"
{code}

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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message