[
https://issues.apache.org/jira/browse/FELIX-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralf Steppacher updated FELIX-4669:
-----------------------------------
Description:
When embedding 3rd party JARs into a bundle, one ends up with Import-Package
entries for all referenced packages in those JARs. The entries are generated
the same, irrespective of whether the package can be resolved in the Maven
dependencies or not.
In order to avoid a potentially long list of explicit import statements like
{code:xml}
<Import-Package>
COM.jrockit.reflect;
resolution:=optional,
COM.newmonics.PercClassLoader;
resolution:=optional,
com.google.gson;
resolution:=optional,
...,
*
</Import-Package>
{code}
it would be convenient if the imports were generated with resolution:=optional
by default if they cannot be resolved in the Maven dependencies.
was:
When embedding 3rd party JARs into a bundle, one ends up with Import-Package
entries for all referenced packages in those JARs. The entries are generated
the same, irrespective of whether the package can be resolved in the Maven
dependencies or not.
In order to avoid a potentially long list of explicit import statements like
<Import-Package>
COM.jrockit.reflect;
COM.newmonics.PercClassLoader;
com.google.gson;
com.jcraft.jsch;
com.thoughtworks.xstream;
com.tinkerpop.blueprints.impls.sail;
com.vividsolutions.jts.*;
...
resolution:=optional,
*
</Import-Package>
it would be convenient if the imports were generated with resolution:=optional
by default if they cannot be resolved in the Maven dependencies.
> Packages that cannot be resolved in Maven dependencies should have
> resolution:=optional
> ---------------------------------------------------------------------------------------
>
> Key: FELIX-4669
> URL: https://issues.apache.org/jira/browse/FELIX-4669
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
> Reporter: Ralf Steppacher
>
> When embedding 3rd party JARs into a bundle, one ends up with Import-Package
> entries for all referenced packages in those JARs. The entries are generated
> the same, irrespective of whether the package can be resolved in the Maven
> dependencies or not.
> In order to avoid a potentially long list of explicit import statements like
> {code:xml}
> <Import-Package>
> COM.jrockit.reflect;
> resolution:=optional,
> COM.newmonics.PercClassLoader;
> resolution:=optional,
> com.google.gson;
> resolution:=optional,
> ...,
> *
> </Import-Package>
> {code}
> it would be convenient if the imports were generated with
> resolution:=optional by default if they cannot be resolved in the Maven
> dependencies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
