From dev-return-39041-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Mon Sep 5 11:31:01 2011 Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2B37A8154 for ; Mon, 5 Sep 2011 11:31:01 +0000 (UTC) Received: (qmail 92535 invoked by uid 500); 5 Sep 2011 11:30:58 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 92285 invoked by uid 500); 5 Sep 2011 11:30:44 -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 92263 invoked by uid 99); 5 Sep 2011 11:30:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Sep 2011 11:30:40 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of pajbam@gmail.com designates 209.85.215.170 as permitted sender) Received: from [209.85.215.170] (HELO mail-ey0-f170.google.com) (209.85.215.170) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Sep 2011 11:30:31 +0000 Received: by eyd10 with SMTP id 10so3568844eyd.1 for ; Mon, 05 Sep 2011 04:30:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer; bh=X3/3JTe44JB8DqJcx4cxzhGCdrbvlZ9ORyzYTf/swX0=; b=au+um1Ntk85zvIf3XuGCEGx3KBo37myKxmwAPwk8fwhmdCGKQN1uwOcYT5I6Vlp1QX AqaZXFHbUEcRmMnLAPV7iK7P+L2Qt8BZPeRao8VFLWp+FZJe8GOHN6aFkzTul2X/m6T5 vL+N78ts+VuzExTrEjWaMTkbnSO+SzoSxxZmA= Received: by 10.213.34.129 with SMTP id l1mr583909ebd.101.1315222210672; Mon, 05 Sep 2011 04:30:10 -0700 (PDT) Received: from [192.168.0.52] (lon92-10-78-226-4-211.fbx.proxad.net [78.226.4.211]) by mx.google.com with ESMTPS id d12sm9479460eeb.8.2011.09.05.04.30.08 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 05 Sep 2011 04:30:09 -0700 (PDT) Sender: Pierre-Arnaud Marcelot From: Pierre-Arnaud Marcelot Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-1--239925692 Subject: Re: svn commit: r1164361 - in /directory/apacheds/trunk: installers-maven-plugin/pom.xml installers/pom.xml Date: Mon, 5 Sep 2011 13:30:06 +0200 In-Reply-To: <36E4BCDA-3824-429C-BAC7-15880DECABE6@marcelot.net> To: Apache Directory Developers List References: <20110902064207.A54C923889E3@eris.apache.org> <34872A70-8885-4C68-A60E-E7ADD64CAB07@marcelot.net> <36E4BCDA-3824-429C-BAC7-15880DECABE6@marcelot.net> Message-Id: X-Mailer: Apple Mail (2.1084) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-1--239925692 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Done at revision 1165244. http://svn.apache.org/viewvc?rev=3D1165244&view=3Drev I re-integrated the 'installers-maven-plugin' and 'installers' = sub-modules in the default build. Installers generation is triggered by the use of the 'installers' = profile ('-Pinstallers'). This will avoid the pom.xml files of these two sub-modules not to be = updated when releasing a new version. Regards, Pierre-Arnaud On 5 sept. 2011, at 09:05, Pierre-Arnaud Marcelot wrote: > On 2 sept. 2011, at 20:11, Stefan Seelmann wrote: >=20 >> On Fri, Sep 2, 2011 at 1:43 PM, Pierre-Arnaud Marcelot = wrote: >>> Hi Stefan, >>>=20 >>> On 2 sept. 2011, at 08:42, seelmann@apache.org wrote: >>>=20 >>>> Author: seelmann >>>> Date: Fri Sep 2 06:42:07 2011 >>>> New Revision: 1164361 >>>>=20 >>>> URL: http://svn.apache.org/viewvc?rev=3D1164361&view=3Drev >>>> Log: >>>> Bump up to current snapshot version. Seems the maven release = process doesn't update those guys. >>>=20 >>> That's because these two projects are not part of the main build by = default. >>> They are triggered by an 'installers' profile in the pom.xml: >>>>> >>>>> >>>>> installers >>>>> >>>>> installers-maven-plugin >>>>> installers >>>>> >>>>> >>>>> >>=20 >> Ok, I understand. >>=20 >>> Maybe we should include by default those modules in the main build, = *but* then trigger to generation of the installers via the 'installers' = profile in the 'installers' module. >>=20 >> Makes sense but I don't understand the implications yet. Is the >> 'installers' profile then automatically activated when building the >> release so that the installers are automatically generated when >> cutting a release? Or should/must this be done manually? >=20 > It would stay the same as it is right now. It won't be generated by = default. >=20 > I think it's better to keep this a manual task. > Especially because the release manager may not have all the required = utilities (dpkg, rpmbuild, packageMaker, etc.) on his machine. >=20 > Regards, > Pierre-Arnaud >=20 >> Kind Regards, >> Stefan >=20 --Apple-Mail-1--239925692 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Done = at revision 1165244.


I re-integrated the 'installers-maven-plugin' and 'installers' = sub-modules in the default build.
Installers generation is = triggered by the use of the 'installers' profile = ('-Pinstallers').

This will avoid the pom.xml = files of these two sub-modules not to be updated when releasing a new = version.

Regards,
Pierre-Arnaud

On 5 sept. 2011, at 09:05, Pierre-Arnaud Marcelot = wrote:

On 2 sept. 2011, at 20:11, Stefan Seelmann = wrote:

On Fri, Sep 2, 2011 at 1:43 PM, = Pierre-Arnaud Marcelot <pa@marcelot.net> = wrote:
Hi Stefan,

On 2 sept. 2011, at 08:42, seelmann@apache.org = wrote:

Author: = seelmann
Date: = Fri Sep  2 06:42:07 = 2011
New = Revision: 1164361

URL: = http://= svn.apache.org/viewvc?rev=3D1164361&view=3Drev
Log:
Bump = up to current snapshot version. Seems the maven release process doesn't = update those guys.

That's because these two = projects are not part of the main build by = default.
They are triggered by an = 'installers' profile in the = pom.xml:
=  <profiles>
=    <profile>
=      <id>installers</id>
=      <modules>
=        <module>installers-maven-p= lugin</module>
=        <module>installers</mod= ule>
=      </modules>
=    </profile>
=  </profiles>

Ok, I understand.

Maybe we should include by default those modules in the = main build, *but* then trigger to generation of the installers via the = 'installers' profile in the 'installers' = module.

Makes sense but = I don't understand the implications yet. Is = the
'installers' profile then = automatically activated when building the
release so that the installers are automatically generated = when
cutting a release? Or = should/must this be done manually?

It would stay the = same as it is right now. It won't be generated by default.

I = think it's better to keep this a manual task.
Especially because the = release manager may not have all the required utilities (dpkg, rpmbuild, = packageMaker, etc.) on his = machine.

Regards,
Pierre-Arnaud

Kind Regards,
Stefan


= --Apple-Mail-1--239925692--