continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Venisse <emman...@venisse.net>
Subject Re: Proposition for CONTINUUM-798
Date Wed, 11 Jul 2007 07:54:31 GMT


Maria Odea Ching a écrit :
> Hi Olivier,
> 
> I think CONTINUUM-798 is for automatic discovery of new modules of a 
> project that is already in Continuum. The current setup is that when 
> Continuum updates from svn, the module is not added as a separate 
> project. Considering CONTINUUM-774, this should only be done if the 
> automaticAddChildModules parameter is set to true right? :-)

Yes, this parameter will be set during the project initialisation, based on the field "load
only root as recursive build". It will be possible to modify it in the edit project screen
too.

Emmanuel
> 
> Thanks,
> Deng
> 
> LAMY Olivier wrote:
>> Hi,
>> IMHO, this can't be "automatic" because CONTINUUM-774 has been fixed.
>> If you use this option this means you don't want to checkout child 
>> modules as a separate project even if it's a new module.
>> A parameter could be add (at the project level) to say something 
>> "automaticAddChildModules" or an other name ;-).
>>
>> -- 
>> Olivier
>> -----Message d'origine-----
>> De : Maria Odea Ching [mailto:oching@exist.com] Envoyé : mercredi 11 
>> juillet 2007 08:41
>> À : Maven Developers List; continuum-dev@maven.apache.org
>> Objet : Proposition for CONTINUUM-798
>>
>> Hi All,
>>
>> I'm trying to fix up http://jira.codehaus.org/browse/CONTINUUM-798,
>> which is "Modules automatic discovery". I think the patch submitted is 
>> already outdated and there was the issue about recursive modules.
>>
>> Anyway, below is how I thought to implement the fix for this:
>>
>> Create an "update-modules" action in continuum-core that will check 
>> for new modules in the pom. The action would be invoked when a project 
>> build is triggered (forced or scheduled), after the project is updated 
>> from SCM (in DefaultBuildController).
>>
>> To add the new module to Continuum, I think we could make use of the
>> addMavenTwoProject(..) method in DefaultContinuum. We can derive the 
>> required parameters from the parent project. The metadata url can be 
>> gotten from the SCM url of the parent  (since the SCM urls of modules 
>> are just constructed from the parent project's SCM url by inserting 
>> the module's name in the url). The group id can also be derived from 
>> the parent project, as well as the SCM username and SCM password.
>>
>> Then after the module is added and checked-out.. the project can just 
>> be added in the build queue so that it will be included in the 
>> triggered build.
>>
>>  From the above implementation, I think we can recurse even through 
>> the modules if they are multi-module projects as well.
>>
>> What do you guys think? Any thoughts would be greatly appreciated :-)
>>
>>
>> Thanks,
>> Deng
>>
>>
>> This e-mail, any attachments and the information contained therein 
>> ("this message") are confidential and intended solely for the use of 
>> the addressee(s). If you have received this message in error please 
>> send it back to the sender and delete it. Unauthorized publication, 
>> use, dissemination or disclosure of this message, either in whole or 
>> in part is strictly prohibited.
>> ********************************************************************** 
>> Ce message électronique et tous les fichiers joints ainsi que  les 
>> informations contenues dans ce message ( ci après "le message" ), sont 
>> confidentiels et destinés exclusivement à l'usage de la  personne à 
>> laquelle ils sont adressés. Si vous avez reçu ce message par erreur, 
>> merci  de le renvoyer à son émetteur et de le détruire. Toutes 
>> diffusion, publication, totale ou partielle ou divulgation sous 
>> quelque forme que se soit non expressément autorisées de ce message, 
>> sont interdites.
>> **********************************************************************
>>
>>   
> 
> 
> 
> 


Mime
View raw message