[
https://issues.apache.org/jira/browse/VFS-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved VFS-448.
------------------------------
Resolution: Fixed
commit -m "Note that [VFS-448] is already fixed: commons-vfs 2.0 JAR has flawed
OSGi MANIFEST.MF."
C:/svn/org/apache/commons/trunks-proper/vfs/src/changes/changes.xml
Sending
C:/svn/org/apache/commons/trunks-proper/vfs/src/changes/changes.xml
Transmitting file data ...
Committed revision 1428361.
> 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 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
