You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Andrew Lindley (JIRA)" <ji...@apache.org> on 2010/12/17 17:07:01 UTC

[jira] Created: (FELIX-2734) no OBR generation when using packaging 'war' and the maven-war-plugin at provisioning

no OBR generation when using packaging 'war' and the maven-war-plugin at provisioning
-------------------------------------------------------------------------------------

                 Key: FELIX-2734
                 URL: https://issues.apache.org/jira/browse/FELIX-2734
             Project: Felix
          Issue Type: Bug
          Components: Maven Bundle Plugin
    Affects Versions: maven-bundle-plugin-2.0.1, maven-bundle-plugin-2.0.0
         Environment: Windows XP, SP3, Java 1.6.0_23, Apache Maven 2.2.1 (r801777)
            Reporter: Andrew Lindley
            Priority: Minor


I am using <artifactId>maven-ipojo-plugin</artifactId> in combination with the <artifactId>maven-war-plugin</artifactId>
The overall goal is to have a <packaging>war</packaging> which can also be exposed as a bundle.

When using the maven-bundle-plugin for provisioning the war is delivered into the repository but no information is written into the OBR repository.

There's a work-around, where I can manually trigger the OBR data to be written calling:

mvn bundle:deploy-file Dfile=target/planets-services-jtidy-1.0.1-SNAPSHOT.war -DpomFile=pom.xml -Durl=file:///tmp/myOBRRepository 
-DgroupId=planets-suite -DartifactId=planets-services-jtidy -Dversion=1.0.1-SNAPSHOT -Dpackaging=war

I assume this happens on behalf of  a bug / missing feature in the maven-bundle-plugin (handling the OBR generation)

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


[jira] [Resolved] (FELIX-2734) no OBR generation when using packaging 'war' and the maven-war-plugin at provisioning

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

Stuart McCulloch resolved FELIX-2734.
-------------------------------------

    Resolution: Not A Problem

The maven-bundle-plugin has the following goals to install/deploy OBR metadata for the current project:

   org.apache.felix:maven-bundle-plugin:install
   org.apache.felix:maven-bundle-plugin:deploy

These are included in the bundle lifecycle: (used when you set packaging to "bundle")

   META-INF/plexus/components.xml

but you can also invoke them separately if you want to use them in your own lifecycle or project executions, such as if you're using  different packaging like "war".

> no OBR generation when using packaging 'war' and the maven-war-plugin at provisioning
> -------------------------------------------------------------------------------------
>
>                 Key: FELIX-2734
>                 URL: https://issues.apache.org/jira/browse/FELIX-2734
>             Project: Felix
>          Issue Type: Bug
>          Components: Maven Bundle Plugin
>    Affects Versions: maven-bundle-plugin-2.0.0, maven-bundle-plugin-2.0.1
>         Environment: Windows XP, SP3, Java 1.6.0_23, Apache Maven 2.2.1 (r801777)
>            Reporter: Andrew Lindley
>            Priority: Minor
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> I am using <artifactId>maven-ipojo-plugin</artifactId> in combination with the <artifactId>maven-war-plugin</artifactId>
> The overall goal is to have a <packaging>war</packaging> which can also be exposed as a bundle.
> When using the maven-bundle-plugin for provisioning the war is delivered into the repository but no information is written into the OBR repository.
> There's a work-around, where I can manually trigger the OBR data to be written calling:
> mvn bundle:deploy-file Dfile=target/planets-services-jtidy-1.0.1-SNAPSHOT.war -DpomFile=pom.xml -Durl=file:///tmp/myOBRRepository 
> -DgroupId=planets-suite -DartifactId=planets-services-jtidy -Dversion=1.0.1-SNAPSHOT -Dpackaging=war
> I assume this happens on behalf of  a bug / missing feature in the maven-bundle-plugin (handling the OBR generation)

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira