[jira] Closed: (FELIX-267) Improve handling of non-bundle / bundle dependencies

["Stuart McCulloch (JIRA)" <ji...@apache.org>]

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

Stuart McCulloch closed FELIX-267.
----------------------------------

    Resolution: Incomplete

Automatic embedding of dependent libraries is difficult to get right for everyone - it's much simpler to keep the current behaviour (which follows the maven rules for the compilation classpath, and bnd rules for what gets pulled into the bundle) and let people handle their own specific cases outside of the bundle plugin.

Hence, I've decided to close this issue as the problem description is still vague and I don't think it adds much value to the plugin.

> Improve handling of non-bundle / bundle dependencies
> ----------------------------------------------------
>
>                 Key: FELIX-267
>                 URL: https://issues.apache.org/jira/browse/FELIX-267
>             Project: Felix
>          Issue Type: Improvement
>          Components: Maven Bundle Plugin
>    Affects Versions: 0.8.0
>         Environment: N/A
>            Reporter: Stuart McCulloch
>             Fix For: 1.0.0
>
>
> The Pax-Wicket folks have suggested the maven-bundle-plugin should include any runtime dependencies in the finished bundle, and that they should also appear on the Bundle-ClassPath. Such dependencies are typically accessed via Class.forName, which means they are not required at compile time, but are also not provided by the framework or other bundles (hence the runtime scope).
> One solution would be to copy the jarfiles to a 'lib' directory under the build, and add a Include-Resource: lib=lib option to the default properties. Each jarfile would also need to be appended to the default Bundle-ClassPath.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.