Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (nike.apache.org: domain of pajbam@gmail.com designates
 209.85.161.50 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:from:mime-version:content-type:subject:date:in-reply-to:to
         :references:message-id:x-mailer;
        b=VVDF38FkBEibo1mvLoq+92eB3+jXaT/4FS7mhjTw9WoTSVbB04/DCTA4GXb5PH2dr2
         YYtpQ6EaAGxuj7G/0P+D9IlcnS7tWEiePOcDWmTETtvAlZmCdR7uDPQi1LMbjqBV3xVE
         7svV2dNzNQxSIwkSm6wXmVUJOvd4CZSMaYYKg=
Sender: Pierre-Arnaud Marcelot <pajbam@gmail.com>
From: Pierre-Arnaud Marcelot <pa@marcelot.net>
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-3-772479935
Subject: Re: [DISCUSS] [Release Scheme] Contract/Policy with users for
 releases
Date: Tue, 11 Jan 2011 16:29:36 +0100
In-Reply-To: <AANLkTimeU-kS=UroFK_aJ=f5rDipoQNTD=YjQd0VbGOk@mail.gmail.com>
To: "Apache Directory Developers List" <dev@directory.apache.org>
References: <AANLkTi=FHepcTbRFxwEQYzOTXmn3KqaosG826+m0pZMO@mail.gmail.com>
 <AANLkTinbeDvC94=kPMoxTX1ABSE99bA34cQfR2jDbhzV@mail.gmail.com>
 <AANLkTinQ7qrKj-NV5urEqv=EB5wH9GRKd1vg2xy_5ds4@mail.gmail.com>
 <AANLkTi=oUbLYQF1JDMDFdwjAxg=b_4RR40Zr3gSOjitg@mail.gmail.com>
 <AANLkTimydD6hTgzf6cUQ8mjMDMRkoobwPAGFi4hatdG-@mail.gmail.com>
 <AANLkTimeU-kS=UroFK_aJ=f5rDipoQNTD=YjQd0VbGOk@mail.gmail.com>
Message-Id: <5B165694-5AAA-416C-98AE-75C27041B2CF@marcelot.net>


--Apple-Mail-3-772479935
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 5 janv. 2011, at 20:32, Alex Karasulu wrote:

>=20
>=20
> On Wed, Jan 5, 2011 at 9:16 PM, Jesse McConnell =
<jesse.mcconnell@gmail.com> wrote:
> >> Since you have eclipse plugins you ought to
> >> build those with maven + tycho and have a similar and sane =
versioning
> >> system.
> >>
> >
> > I talked with Pierre about it. As a side point because of the way =
the build
> > in Studio is setup, we're unable at this point to take advantage of =
IDE
> > refactoring since dependencies are on bundle jars rather than on =
projects
> > themselves. Do you know if using Maven + Tycho will help with this =
specific
> > problem?
> > I'm asking this because it might spare some work for us when we =
refactor
> > shared which Studio depends on.
> >
>=20
> when I am working on the jetty wtp plugin I am able to have all 3
> plugins open and refactor between them, I just let m2eclipse import
> and do the right thing
>=20
> the combination of m2eclipse + maven3 + tycho is quite nice
>=20
> Ahh cool. PAM, and Seelman is this something you might want to try or =
leave out for later? I just cringe at the thought of your having to =
manually update Studio again after we reorg shared. =20

Hi Alex, Jesse,

The situation is a little more complicated actually as we have a three =
level story here.

Let me recap the situation...

Some functionalities of Studio plugins require that we use/extend =
classes of some Shared and ApacheDS project modules.

Unfortunately, those Shared and ApacheDS project modules are not OSGI =
(or Eclipse) bundles (yet?).
In order to solve that problem and to be able to use them in our =
plugins, we created a specific Eclipse plugin for each required Shared =
and ApacheDS dependency.
I named such a plugin as a "Library Plugin", opposed to our "Studio Code =
Plugins".

A "Library Plugin" simply embeds the jar file of the corresponding =
Shared or ApacheDS project module and sets a proper MANIFEST.MF file =
with the correct OSGI and Eclipse instructions (Bundle-SymbolicName, =
Export-Package, Require-Bundle, etc.).

In the end, in your Eclipse workspace, you find yourself having two =
projects for a single original module:
- that original module with the source code ('shared-ldap' for example)
- the associated library plugin, based on a constructed (snapshot) jar =
file of that original module ('org.apache.directory.shared.ldap' for =
example)

Now, when you refactor the source code of the original module, =
unfortunately, the link between that module and the final "Studio Code =
Plugin" is lost for Eclipse, because of the use of the jar file in the =
associated "Library Plugin" between the two.
Then the modifications applied on the original module are not applied to =
the "Studio Code Plugin".

I'm not sure Tycho can help us solve this issue, but it does, I'd be =
happy to update our Studio build to use it...

Thoughts?

Regards,
Pierre-Arnaud=

--Apple-Mail-3-772479935
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>On 5 janv. 2011, at 20:32, Alex Karasulu =
wrote:</div><div><div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><br><br><div class=3D"gmail_quote">On Wed, Jan 5, 2011 at =
9:16 PM, Jesse McConnell <span dir=3D"ltr">&lt;<a =
href=3D"mailto:jesse.mcconnell@gmail.com">jesse.mcconnell@gmail.com</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">&gt;&gt; Since you have eclipse plugins you ought =
to<br>
&gt;&gt; build those with maven + tycho and have a similar and sane =
versioning<br>
&gt;&gt; system.<br>
&gt;&gt;<br>
&gt;<br>
&gt; I talked with Pierre about it. As a side point because of the way =
the build<br>
&gt; in Studio is setup, we're unable at this point to take advantage of =
IDE<br>
&gt; refactoring since dependencies are on bundle jars rather than on =
projects<br>
&gt; themselves. Do you know if using Maven + Tycho will help with this =
specific<br>
&gt; problem?<br>
&gt; I'm asking this because it might spare some work for us when we =
refactor<br>
&gt; shared which Studio depends on.<br>
&gt;<br>
<br>
</div>when I am working on the jetty wtp plugin I am able to have all =
3<br>
plugins open and refactor between them, I just let m2eclipse import<br>
and do the right thing<br>
<br>
the combination of m2eclipse + maven3 + tycho is quite =
nice<br></blockquote><div><br></div><div>Ahh cool. PAM, and Seelman is =
this something you might want to try or leave out for later? I just =
cringe at the thought of your having to manually update Studio again =
after we reorg shared. &nbsp;</div></div></blockquote><br><div>Hi Alex, =
Jesse,</div><div><br></div><div>The situation is a little more =
complicated actually as we have a three level story =
here.</div><div><br></div><div>Let me recap the =
situation...</div><div><br></div><div>Some functionalities of Studio =
plugins require that we use/extend classes of some Shared and ApacheDS =
project modules.</div><div><br></div><div>Unfortunately, those Shared =
and ApacheDS project modules are not OSGI (or Eclipse) bundles =
(yet?).</div><div>In order to solve that problem and to be able to use =
them in our plugins, we created a specific Eclipse plugin for each =
required Shared and ApacheDS dependency.</div><div>I named such a plugin =
as a "Library Plugin", opposed to our "Studio Code =
Plugins".</div><div><br></div><div>A "Library Plugin" simply embeds the =
jar file of the corresponding Shared or ApacheDS project module and sets =
a proper MANIFEST.MF file with the correct OSGI and Eclipse instructions =
(Bundle-SymbolicName,&nbsp;Export-Package, Require-Bundle, =
etc.).</div><div><br></div><div>In the end, in your Eclipse workspace, =
you find yourself having two projects for a single original =
module:</div><div>- that original module with the source code =
('shared-ldap' for example)</div><div>- the associated library plugin, =
based on a constructed (snapshot) jar file of that original module =
('org.apache.directory.shared.ldap' for =
example)</div><div><br></div><div>Now, when you refactor the source code =
of the original module, unfortunately, the link between that module and =
the final "Studio Code Plugin" is lost for Eclipse, because of the use =
of the jar file in the associated "Library Plugin" between the =
two.</div><div>Then the modifications applied on the original module are =
not applied to the "Studio Code Plugin".</div><div><br></div><div>I'm =
not sure Tycho can help us solve this issue, but it does, I'd be happy =
to update our Studio build to use =
it...</div><div><br></div><div>Thoughts?</div><div><br></div><div>Regards,=
</div><div>Pierre-Arnaud</div></div></div></body></html>=

--Apple-Mail-3-772479935--