felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stuart McCulloch (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-433) Bundle Plugin should optionally extract the bundel jar to target/classes
Date Fri, 07 Dec 2007 07:04:43 GMT

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

Stuart McCulloch commented on FELIX-433:

will think about this - you can actually get the same result by using the maven-dependency-plugin
in the project POM to unpack the final artifact to target/classes, which is what a number
of projects do at the moment.

If I do add it I will change the patch, as it currently doesn't allow unpacking of the bundle
and writing of the manifest to another location, which is required for Eclipse/PDE support.

> Bundle Plugin should optionally extract the bundel jar to target/classes
> ------------------------------------------------------------------------
>                 Key: FELIX-433
>                 URL: https://issues.apache.org/jira/browse/FELIX-433
>             Project: Felix
>          Issue Type: New Feature
>          Components: Maven Bundle Plugin
>    Affects Versions: 0.8.0
>            Reporter: Hiram Chirino
>             Fix For: 1.0.0
>         Attachments: FELIX-433.patch
> When using Maven 2.0.7 in a reactor based project, modules that depend on maven-bundle-plugin
modules will be compiled with the classpath set to the project's target/classes directory.
 And since the classes may not be there the module that depends on the bundle fails to compile.

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

View raw message