commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd Eckenfels (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (VFS-448) commons-vfs 2.0 JAR has flawed OSGi MANIFEST.MF
Date Mon, 03 Feb 2014 18:48:10 GMT

    [ https://issues.apache.org/jira/browse/VFS-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13889736#comment-13889736
] 

Bernd Eckenfels commented on VFS-448:
-------------------------------------

Currently the 2.1-SN trunk has common-parent:32 and the effective POM shows maven-bundle-plugin:2.4.0.
However this does not help the situation. 

[~davsclaus], I have not seen a way to honor optional dependencies, can you maybe point us
to a reference whant the plugin would need? Otherwise I would provide a patch using the *;resolution=optional
pattern, but this is a bit ugly as I dont want to maintain mandatotey package list.

> commons-vfs 2.0 JAR has flawed OSGi MANIFEST.MF
> -----------------------------------------------
>
>                 Key: VFS-448
>                 URL: https://issues.apache.org/jira/browse/VFS-448
>             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
(2.3.7).
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message