From dev-return-35273-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Mon Oct 04 17:32:09 2010 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 26149 invoked from network); 4 Oct 2010 17:32:09 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 Oct 2010 17:32:09 -0000 Received: (qmail 25017 invoked by uid 500); 4 Oct 2010 17:32:09 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 24851 invoked by uid 500); 4 Oct 2010 17:32:08 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 24844 invoked by uid 99); 4 Oct 2010 17:32:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Oct 2010 17:32:08 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of akarasulu@gmail.com designates 209.85.216.50 as permitted sender) Received: from [209.85.216.50] (HELO mail-qw0-f50.google.com) (209.85.216.50) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Oct 2010 17:32:02 +0000 Received: by qwg8 with SMTP id 8so4249764qwg.37 for ; Mon, 04 Oct 2010 10:31:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=Z2dcY/wbnj+lJzO5RoCRqrlr5slOIA+kSzz/bSHczu0=; b=siMItaCYig0l+0PSecw3/Ov7Pj79ICCRuCzfCKvGWZBllhKOowmMq+V09UMUWarY+n yzAYw3ftMx1auynS3VmImYNd4jx9309pKQMs6hyobYBUzi0KxGdWIjjJsj69zR6pD/hf c1VrMbNw/RjBroysCQ8tzSc0jMjicfoKRYXfs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=G88ySOegEaoYZeO2tf+SJsrIaTFxyEnN1dwO8U5NmpEtfmJSvQ1ssZWunELkjRhsBd ldsKNDNMa5CLshsrg7tuLloJS5wqDYbaQPEBNpujMspGZuPH0MVhfQGdKh9Q/Xe73xb8 ZwvDY+x/9XkkwrcrKSKmKRdxP7o5saEn4TnOI= MIME-Version: 1.0 Received: by 10.229.185.7 with SMTP id cm7mr7349255qcb.7.1286213501195; Mon, 04 Oct 2010 10:31:41 -0700 (PDT) Sender: akarasulu@gmail.com Received: by 10.229.15.204 with HTTP; Mon, 4 Oct 2010 10:31:41 -0700 (PDT) In-Reply-To: <5AD665B3-F7B0-4EC3-8FD5-1884E0A56C12@marcelot.net> References: <5AD665B3-F7B0-4EC3-8FD5-1884E0A56C12@marcelot.net> Date: Mon, 4 Oct 2010 20:31:41 +0300 X-Google-Sender-Auth: 80EoU7tggLCPhtFAI8v8LZikqzg Message-ID: Subject: Re: [ApacheDS] Installers refactored for 2.0 + Future for installers and daemon subprojects From: Alex Karasulu To: Apache Directory Developers List Content-Type: multipart/alternative; boundary=0016e6509e42d819490491cdeaa6 X-Virus-Checked: Checked by ClamAV on apache.org --0016e6509e42d819490491cdeaa6 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Oct 4, 2010 at 6:38 PM, Pierre-Arnaud Marcelot wrote: > Hi Dev, > > That's it. > I'm done with the refactoring of the installers. > > The new installers are now integrated in the ApacheDS subproject (which > make the two other subprojects, daemon and installers, obsolete). > > Four new projects have been created. > > First, the 'apacheds-service' project (equivalent to the 'apacheds-noarch' > project in the installers subproject). > It contains the ApacheDsService class which holds all the code to start the > server as well as Installation and Instance layout classes. > This jar is now packaged as a shaded jar which includes and embeds all the > needed dependencies. > > Secondly, the 'apacheds-wrapper' project (equivalent to the > 'daemon-bootstrappers' project in the daemon subproject). > This is an implementation of a Tanuki service wrapper for ApacheDS. > I've removed all other old implementation (JSVC, ProcRun) and cleaned up > the code to only support Tanuki. > > Thirdly, the 'apacheds-installers-maven-plugin' project (equivalent to the > 'daemon-plugin' project in the daemon subproject). > This maven plugin is responsible for creating the installers. > Again, I tried to clean a lot of things there. > Now, everything is included in the maven plugin (before, files were shared > between the plugin and the project which was calling it). > A lot of configuration files are now shared between installer types > (before, most of them were duplicated, one for each type of installer) > > Lastly, the 'apacheds-installers' project (equivalent to the 'apacheds' > project in the installers subproject). > This is the project where we call the apacheds-installers-maven-plugin and > ask him to generate the installers we want. > > The two first new projects (apacheds-service and apacheds-wrapper) are > included in the standard build while the two last > (apacheds-installers-maven-plugin and apacheds-installers) are activated > with an 'installers' profile defined on the root pom. > > I have created a page explaining how to generate and use installers [1]. > Good news, I can now build all installers (for all operating systems) on my > Mac in less than a minute. :) > > Thoughts? > > Nice job on the cleanup. This simplifies so much thanks Pierre! > > Now that this refactoring is done, I think the 'installers' subproject can > now be removed. > I'd say the same thing for the 'daemon' subproject but AFAIR we were not > the only one using the daemon-plugin. I believe the Felix project was using > it a while ago but I don't know if it's still the case. > I think Karaf might have done away with that. However it does not hurt to just move it to the sandbox or delete it from svn. I'm sure if they are using it they would stick to a revision. If they need it we can figure something out. > If they're still using it I think it safe that we keep it, even if it will > probably not be updated and/or maintained, if not, I'd rather remove it. > > Thoughts? > > Go ahead and remove it - not going to be lost for ever with svn. Thanks again mate. -- Alex Karasulu My Blog :: http://www.jroller.com/akarasulu/ Apache Directory Server :: http://directory.apache.org Apache MINA :: http://mina.apache.org To set up a meeting with me: http://tungle.me/AlexKarasulu --0016e6509e42d819490491cdeaa6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Mon, Oct 4, 2010 at 6:38 PM, Pierre-Arnaud Ma= rcelot <pa@marcelot= .net> wrote:
Hi Dev,

That's it.
I'm done with the refactoring of the installers.

The new installers are now integrated in the ApacheDS subproject (which mak= e the two other subprojects, daemon and installers, obsolete).

Four new projects have been created.

First, the 'apacheds-service' project (equivalent to the 'apach= eds-noarch' project in the installers subproject).
It contains the ApacheDsService class which holds all the code to start the= server as well as Installation and Instance layout classes.
This jar is now packaged as a shaded jar which includes and embeds all the = needed dependencies.

Secondly, the 'apacheds-wrapper' project (equivalent to the 'da= emon-bootstrappers' project in the daemon subproject).
This is an implementation of a Tanuki service wrapper for ApacheDS.
I've removed all other old implementation (JSVC, ProcRun) and cleaned u= p the code to only support Tanuki.

Thirdly, the 'apacheds-installers-maven-plugin' project (equivalent= to the 'daemon-plugin' project in the daemon subproject).
This maven plugin is responsible for creating the installers.
Again, I tried to clean a lot of things there.
Now, everything is included in the maven plugin (before, files were shared = between the plugin and the project which was calling it).
A lot of configuration files are now shared between installer types (before= , most of them were duplicated, one for each type of installer)

Lastly, the 'apacheds-installers' project (equivalent to the 'a= pacheds' project in the installers subproject).
This is the project where we call the apacheds-installers-maven-plugin and = ask him to generate the installers we want.

The two first new projects (apacheds-service and apacheds-wrapper) are incl= uded in the standard build while the two last (apacheds-installers-maven-pl= ugin and apacheds-installers) are activated with an 'installers' pr= ofile defined on the root pom.

I have created a page explaining how to generate and use installers [1]. Good news, I can now build all installers (for all operating systems) on my= Mac in less than a minute. :)

Thoughts?


Nice job on the cleanup. This simplifi= es so much thanks Pierre!
=A0
If they're still using it= I think it safe that we keep it, even if it will probably not be updated a= nd/or maintained, if not, I'd rather remove it.

Thoughts?


Go ahead and remove it - not going to = be lost for ever with svn.

Thanks agai= n mate.

--
Alex Karasulu
My Blog :: http://www.jroller.com/akarasulu/ Apache Directory Server :: http://d= irectory.apache.org
Apache MINA :: http://mina.apache.org
To set up a meeting with me: http://tungle.me/AlexKarasulu
--0016e6509e42d819490491cdeaa6--