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 (athena.apache.org: domain of pajbam@gmail.com designates
 74.125.82.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=hW8053wu72zufQ9kZJOS9OwtRQdqGFnFUWwFY/GG6ymEVhHxrAqyrcraZmLk13G8gK
         G6rbA4bQftvdXsCYZdcq6lCR8rGsCkDocH9mrn3vtiImzpgqNZHOwiioVUEknZNhmcNZ
         MRfU4J4tgyWA2ApqydID4v8WlOfj2s80bwnbQ=
Sender: Pierre-Arnaud Marcelot <pajbam@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: [DISCUSS] [Release Scheme] Contract/Policy with users for
 releases
From: Pierre-Arnaud Marcelot <pa@marcelot.net>
In-Reply-To: <AANLkTimP=0B3mj2TSd4CD---B0GY1yURh2kt2fD9P6sU@mail.gmail.com>
Date: Tue, 11 Jan 2011 17:06:02 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <49A367E6-E59B-4A2D-9DF2-DF835818BFAD@marcelot.net>
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>
 <5B165694-5AAA-416C-98AE-75C27041B2CF@marcelot.net>
 <AANLkTimP=0B3mj2TSd4CD---B0GY1yURh2kt2fD9P6sU@mail.gmail.com>
To: "Apache Directory Developers List" <dev@directory.apache.org>

Yeah, making the original artifacts OSGI bundles would be the ideal =
solution.
It may also be the easiest one (moving our current build to Tycho might =
not be trivial).

I'll try to evaluate Tycho more in depth later this month and ask the =
Tycho guys about it.

Thanks,
Pierre-Arnaud


On 11 janv. 2011, at 16:42, Jesse McConnell wrote:

> my recommendation would be to reach out to the tycho guys for a bit of
> advice on this...I suspect the thing to do is to make the original
> artifacts also osgi bundles, it really isn't that hard with the felix
> maven bundle plugin, but there might be another way they could
> recommend doing it
>=20
> jesse
>=20
>=20
> --
> jesse mcconnell
> jesse.mcconnell@gmail.com
>=20
>=20
>=20
> On Tue, Jan 11, 2011 at 09:29, Pierre-Arnaud Marcelot =
<pa@marcelot.net> wrote:
>> 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:
>>>=20
>>>>> Since you have eclipse plugins you ought to
>>>>> build those with maven + tycho and have a similar and sane =
versioning
>>>>> system.
>>>>>=20
>>>>=20
>>>> 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
>>>=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