Mailing-List: contact users-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@felix.apache.org
Received-SPF: pass (nike.apache.org: domain of guillaume.ow2@gmail.com
 designates 209.85.212.175 as permitted sender)
MIME-Version: 1.0
Sender: guillaume.ow2@gmail.com
In-Reply-To: 
 <CAKjwzko6uveVcBACvnMuz5N_GX0WHSdS=Bi=6Gt8x1XzYwX6ug@mail.gmail.com>
References: 
 <CAKjwzkoPAWzaaMyYU3dTvu1dqXiw-ec+8yoh5QqDWqDGTzQfXQ@mail.gmail.com>
	<4F9953D4-0C1C-48B7-B14E-900B67604408@gmail.com>
	<CAKjwzkq5GfP06ioZOrm_BsP7w4c88vLi7uk_eMJWurbq1BwmHA@mail.gmail.com>
	<FBA43D7A-9B3A-4367-B88E-D3F3760B14E1@gmail.com>
	<CAKjwzkpYGsxdHRDchWf=eLFad6dAvH_ywv9fi9YuJw=ZLTCNpA@mail.gmail.com>
	<97C6E57B-5F98-4C4F-9FAB-58759A47B49B@gmail.com>
	<CAKjwzko6uveVcBACvnMuz5N_GX0WHSdS=Bi=6Gt8x1XzYwX6ug@mail.gmail.com>
Date: Thu, 12 Apr 2012 09:53:21 +0200
Message-ID: 
 <CAG1yf3PYs+GO2P89sUGfd76QkQ4WABNqe5BRJbyLX1q_-CwfPA@mail.gmail.com>
Subject: Re: IPojo manipulated bundle not synched with project folder contents
From: "Guillaume Sauthier (Objectweb)" <guillaume.sauthier@objectweb.org>
To: users@felix.apache.org
Content-Type: multipart/alternative; boundary=f46d043892ab5473bc04bd76a641

--f46d043892ab5473bc04bd76a641
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

What about using the ipojo-bnd-plugin (there is a recent thread on
users@felix with configuration details) ?
It directly executes iPOJO manipulation inside the maven-bundle-plugin, so
it follow the behavior dictated by the bnd configuration.

--G

2012/4/11 G=F6kt=FCrk Gezer <gokturk.gezer@gmail.com>

> Hi Clement,
>
>
> > > Question is, in which shape we should integrate that facility into
> maven
> > > build:
> > > * A new goal for directoryManipulation for use in 'compile' phase
> > > * A new boolean property for ipojo-bundle goal to unpack manipulated
> > > content into project folder
> > > * Modification of current mojo to also accept directory paths as
> > > manipulation candidate
> > > * Or combination of above approaches,
> > >
> >
> > So, I will eliminate 2 because of the overhead. I would be in favor of =
1
> > because you don't actually have to package the bundle to get it to work=
,
> > however it requires the manifest to be updated too. I'm not sure that
> this
> > is actually possible.
> >
> I reconsidered the option-1 today and yeah, it seems non-trivial just
> inside maven-ipojo-plugin. But i've managed to implement the option-1 tha=
t
> way:
>
> *Created a new goal "ipojo-manipulate" in "process-classes" phase, which
> extends maven-bundle-plugin's "manifest" goal. Plugin property propagatio=
n
> is managed by maven-inherit-plugin added to parent pom.
> *As i see maven-ipojo-plugin is beeing used with maven-bundle-plugin
> generally. So i read the maven-bundle-plugin configuration in pom.xml
> inside "ipojo-manipulate" mojo to issue a MANIFEST file generation.
> If pom.xml does not contain maven-bundle-plugin instructions then MANIFES=
T
> is generated with default values by bnd.
> *Then manipulate the class contents and MANIFEST file using
> directoryManipulation();
>
> In my experiments, manipulated contents and MANIFEST work just fine after
> maven-bundle-plugin:bundle without maven-ipojo-plugin:ipojo-bundle after
> packaging.
>
> When configured correctly with m2e plugin, i believe that this new goal c=
an
> replace ipojo-ant task inside eclipse. But i don't know it for sure, didn=
't
> tried it yet, since i don't know how m2e's MavenBuilder works internally.
>
> One problem with the implementation comes from
> DirectoryResourceStore.open() method, since it is writing manipulated
> MANIFEST to a fixed location rather then altering given MANIFEST. So i
> added a additional field to DirectoryResourceStore to keep MANIFEST file'=
s
> path, then used it. However i don't know if i'm breaking some intended
> behavior here?
>
> Please let me know WDYT about that approach in theory ...
>
> From my favorite to less favorite:  1 - 3 - 2.
>
>
> > Regards,
> >
> > Clement
> >
> >
>

--f46d043892ab5473bc04bd76a641--