[jira] [Resolved] (VFS-498) OSGI MANIFEST.MF "Import-Package" should be ";resolution:=optional" for Maven "optional" dependencies

["Bernd Eckenfels (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/VFS-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bernd Eckenfels resolved VFS-498.
---------------------------------
       Resolution: Fixed
         Assignee: Bernd Eckenfels
    Fix Version/s: 2.1

Fixed by Commit r1688726 and r1695539.

http://svn.apache.org/r1688726
http://svn.apache.org/r1695539

Some extra HDFS integration testing would be good.

> OSGI MANIFEST.MF "Import-Package" should be ";resolution:=optional" for Maven "optional" dependencies
> -----------------------------------------------------------------------------------------------------
>
>                 Key: VFS-498
>                 URL: https://issues.apache.org/jira/browse/VFS-498
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Michael Schnell
>            Assignee: Bernd Eckenfels
>             Fix For: 2.1
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> In the Maven "pom.xml" there are several "optional" dependencies like "jsch":
> {quote}
>     <dependency>
>       <groupId>com.jcraft</groupId>
>       <artifactId>jsch</artifactId>
>       <optional>true</optional>
>     </dependency>
> {quote}
> In the "Import-Package" section of the MANIFEST.MF it should also be "optional" like this:
> {quote}
> com.jcraft.jsch;resolution:=optional,
> {quote}
> At the moment all dependencies are always required. This is a problem if you want to use VFS in an OSGI environment as you have to install ALL dependencies and not only the ones you really need.
> The mechanism creating the MANIFEST should be adjusted to reflect the optional dependencies also in the MANIFEST. (Unfortunatelly this could mean to list all packages which should be optional).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)