You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2007/12/06 16:45:43 UTC

[jira] Created: (FELIX-433) Bundle Plugin should optionally extract the bundel jar to target/classes

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


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.


[jira] Updated: (FELIX-433) Bundle Plugin should optionally extract the bundel jar to target/classes

Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart McCulloch updated FELIX-433:
-----------------------------------


Hi,

I'd like to get all resolved defects verified before releasing the 1.1.0 version of the bundleplugin - so I'd really appreciate it if you could check things are still ok with the current snapshot, and if so close off the defect.

Thanks in advance!

> 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
>            Assignee: Stuart McCulloch
>             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.


[jira] Resolved: (FELIX-433) Bundle Plugin should optionally extract the bundel jar to target/classes

Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart McCulloch resolved FELIX-433.
------------------------------------

    Resolution: Fixed

I tidied up the patch and changed the option to be unpackBundle, as that is more in keeping with other names.

> 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
>            Assignee: Stuart McCulloch
>             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.


[jira] Updated: (FELIX-433) Bundle Plugin should optionally extract the bundel jar to target/classes

Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino updated FELIX-433:
--------------------------------

    Attachment: FELIX-433.patch

This patch adds a 'extractBundle' configuration option to the plugin.  Off by default but when enabled it will extract the bundle jar to the target/classes directory.

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


[jira] Assigned: (FELIX-433) Bundle Plugin should optionally extract the bundel jar to target/classes

Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart McCulloch reassigned FELIX-433:
--------------------------------------

    Assignee: Stuart McCulloch

> 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
>            Assignee: Stuart McCulloch
>             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.


[jira] Closed: (FELIX-433) Bundle Plugin should optionally extract the bundel jar to target/classes

Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stuart McCulloch closed FELIX-433.
----------------------------------


> 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
>            Assignee: Stuart McCulloch
>             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.


[jira] Work started: (FELIX-433) Bundle Plugin should optionally extract the bundel jar to target/classes

Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on FELIX-433 started by Stuart McCulloch.

> 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
>            Assignee: Stuart McCulloch
>             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.


[jira] Commented: (FELIX-433) Bundle Plugin should optionally extract the bundel jar to target/classes

Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Work stopped: (FELIX-433) Bundle Plugin should optionally extract the bundel jar to target/classes

Posted by "Stuart McCulloch (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on FELIX-433 stopped by Stuart McCulloch.

> 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
>            Assignee: Stuart McCulloch
>             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.