directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pierre-Arnaud Marcelot ...@marcelot.net>
Subject Re: svn commit: r1164361 - in /directory/apacheds/trunk: installers-maven-plugin/pom.xml installers/pom.xml
Date Mon, 05 Sep 2011 07:05:09 GMT
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=1164361&view=rev
>>> 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-plugin</module>
>>>>         <module>installers</module>
>>>>       </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


Mime
View raw message