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] [Updated] (VFS-498) OSGI MANIFEST.MF "Import-Package" should be ";resolution:=optional" for Maven "optional" dependencies
Date Wed, 31 Dec 2014 05:01:13 GMT

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

Bernd Eckenfels updated VFS-498:
--------------------------------
    Description: 
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).


  was:
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.



> 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. (Unfortunatelly this could mean to list all packages which should be
optional).



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

Mime
View raw message