Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <13118997.1197274123141.JavaMail.jira@brutus>
Date: Mon, 10 Dec 2007 00:08:43 -0800 (PST)
From: "Guillaume Sauthier (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Resolved: (FELIX-432) Add an option that allow the
 manipulated bundle to be attached to the project
In-Reply-To: <10519226.1196949343361.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Guillaume Sauthier resolved FELIX-432.
--------------------------------------

    Resolution: Fixed

It works perfectly.
Thanks you Clement

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