You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Arnaud MERGEY (JIRA)" <ji...@apache.org> on 2018/03/05 11:03:00 UTC

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

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

Arnaud MERGEY updated VFS-655:
------------------------------
    Fix Version/s:     (was: 2.1)

> OSGI MANIFEST.MF "Import-Package" should be ";resolution:=optional" for Maven "optional" dependencies
> -----------------------------------------------------------------------------------------------------
>
>                 Key: VFS-655
>                 URL: https://issues.apache.org/jira/browse/VFS-655
>             Project: Commons VFS
>          Issue Type: Bug
>    Affects Versions: 2.2
>            Reporter: Arnaud MERGEY
>            Assignee: Bernd Eckenfels
>            Priority: Major
>   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
(v7.6.3#76005)