felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Sauthier (JIRA)" <j...@apache.org>
Subject [jira] Updated: (FELIX-432) Add an option that allow the manipulated bundle to be attached to the project
Date Thu, 06 Dec 2007 15:56:42 GMT

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

Guillaume Sauthier updated FELIX-432:
-------------------------------------

    Attachment: maven-ipojo-plugin2.patch

A new version of the patch using the alternate proposition: using a 'classifier' parameter.


> Add an option that allow the manipulated bundle to be attached to the project
> -----------------------------------------------------------------------------
>
>                 Key: FELIX-432
>                 URL: https://issues.apache.org/jira/browse/FELIX-432
>             Project: Felix
>          Issue Type: Improvement
>          Components: iPOJO
>         Environment: Affect iPOJO 0.7.5 SNAPSHOT
>            Reporter: Guillaume Sauthier
>         Attachments: maven-ipojo-plugin.patch, maven-ipojo-plugin2.patch
>
>
> I would like to be able to have a separate jar file for the output of iPOJO.
> I explain the idea: I want to have 2 output artifacts from my iPOJO project: the first
one is the bundle that is produced by Bnd, and the second one is the same bundle, but iPOJOized
(manipulated).
> That will be useful if I want to test my bundle in a non-ipojo env. Or if the env is
not even OSGi.

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


Mime
View raw message