[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13889740#comment-13889740 ] 

Bernd Eckenfels commented on VFS-498:
-------------------------------------

I added this to VFS-448 as there was a solution suggested there but it seems not to work without additional work:

{quote}
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.
Claus Ibsen, 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.
{quote}

> 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
>   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. This could be done for example by using "maven-bundle-plugin" to automate the generation.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)