commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (VFS-448) commons-vfs 2.0 JAR has flawed OSGi MANIFEST.MF
Date Thu, 03 Jan 2013 14:50:12 GMT


Claus Ibsen commented on VFS-448:

Hi Gary

Thanks for reacting.

I went down another path and used the 2.0 GA release. The "flawed" OSGI metadata caused me
to add a zillion extra bundles which is marked as optional in the Maven pom.xml file. But
is mandatory in OSGi. 

And some of them had the same issue, so that added another extra set of bundles, and so forth.
Not ideal but I can get around so far, as I prefer to use a release which is in maven central.

It was in fact a flawed Apache Hadoop HDFS bundle that started this, and lead me down to VFS2,
and other Apache projects having this issue.

Its for the Apache Camel project where we have a number of Camel components ready to install
in OSGi as Apache Karaf "features". And so we have a camel-hdfs component, that lead me to
report this ticket.

Good to know you guys are back working on commons VFS, as we have reopened a ticket in Camel
to work on a camel-vfs component. That would allow Camel to work easier with compressed files,
and what else you guys have in your project. So kudos for getting back.
> commons-vfs 2.0 JAR has flawed OSGi MANIFEST.MF
> -----------------------------------------------
>                 Key: VFS-448
>                 URL:
>             Project: Commons VFS
>          Issue Type: Improvement
>    Affects Versions: 2.0
>            Reporter: Claus Ibsen
>              Labels: osgi
>             Fix For: 2.1
> Hi
> The 2.0 release has a problem as its build using an older Felix Bundle plugin which you
guys inheirt from the parent pom.xml which is version 21
> org.apache.commons:commons-parent:21
> That uses felix bundle plugin 1.4.3 which unfortunately does not honor the maven dependencies
at <scope>option</scope>, but instead marks the osgi meta-data as mandatory imports.
> This means using commons-vfs 2.0 release in OSGi is hard, as you need all the 3rd party
JARS and they should be OSGi bundles as well, and they may have flaws as well. So it just
goes again.
> I suggest to upgrade to parent:27 or better which is using the latest Felix Bundle plugin
> It would be lovely if you guys would release a new release with the osgi metadata fixed.
Then people can use it in OSGi. If not they can't really do that.

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:

View raw message