felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Yakop (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-267) Add runtime dependencies to the Bundle-ClassPath, and include them in the bundle
Date Fri, 06 Apr 2007 09:33:32 GMT

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

Edward Yakop commented on FELIX-267:

In pax-wicket issue, the wicket jars are marked as "compile", as they are needed to compile
the pax-wicket code. Hence, it should read "include any dependencies that have scope as [not
provided] and [not test] in the finished bundle ...."

> Add runtime dependencies to the Bundle-ClassPath, and include them in the bundle
> --------------------------------------------------------------------------------
>                 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
> 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.

View raw message