continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Emmanuel Venisse <emman...@venisse.net>
Subject Re: multi-module maven 2 project
Date Tue, 31 Jan 2006 08:46:10 GMT
a "command line project" is a Shell project.

If you want to build all sub-modules when you  build the parent, you have several solution.

1- You want all projects are independant in Continuum, so you add a Maven project. The default
goal 
of a maven parent project isclean install with -N parameter that means that mvn doesn't run

recursivly in all modules. You can remove -N parameter in build definition but all your submodules

will be built twice (with parent pom and with independant project)

2- You don't need independant projects for submodules in Continuum. Add a Shell project instead
of 
Maven project and set up the command line to run.

Emmanuel

Johnson, Jonathan a écrit :
> I submitted the parent pom to continuum.  Its very nicely found all the sub-modules and
set those up as well.  I did not have to set up a command line project (not sure what that
is either).
> 
> One thing that could be enhanced for continuum is a tree structure instead of a flat
list.  The tree structure would indicate while module is the parent module.  Currently there
is not indicator which is you parent module.  Of course that begs the question of a hierarchical,
multi-project tree in maven and continuum.
> 
> The other thing I noticed is forcing a build on the parent module in continuum does not
execute the build on the all children.  For me it quickly executes with a success yet the
sub-module builds are not invoked.  
> 
> This is the build report on the parent module named "Java Modules".
> 
> 
> [INFO] Scanning for projects...
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Java Modules
> [INFO]    task-segment: [clean, install]
> [INFO] ----------------------------------------------------------------------------
> [INFO] [clean:clean]
> [INFO] Skipping missing optional mojo: org.apache.maven.plugins:maven-site-plugin:attach-descriptor
> [INFO] [install:install]
> [INFO] Installing /home/builder/454/AppJava/modules/66/pom.xml to /home/builder/.m2/repository/com/fourfivefour/AppJavaModules/1.0/AppJavaModules-1.0.pom
> [INFO] ----------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO] ----------------------------------------------------------------------------
> [INFO] Total time: 2 seconds
> [INFO] Finished at: Mon Jan 30 14:02:38 EST 2006 [INFO] Final Memory: 2M/5M [INFO] ------------------------------------------------------------------------
> 
> -----Original Message-----
> From: Stevenson, Chris [mailto:Chris.Stevenson@DrKW.com] 
> Sent: Monday, January 30, 2006 1:04 PM
> To: 'continuum-users@maven.apache.org'
> Subject: RE: multi-module maven 2 project
> 
> Gents,
> 
> Can I just check, did you setup your mvn multi module project by submitting
> the parent pom and continuum working it out? Or did you have to create a
> command line project? 
> 
> I remember a while back that continuum couldn't build multi module projects,
> except as a command line project..... Or am I going nuts..
> 
> Chris
> 
> -----Original Message-----
> From: Johnson, Jonathan [mailto:jjohnson@454.com] 
> Sent: 27 January 2006 15:26
> To: continuum-users@maven.apache.org
> Subject: RE: multi-module maven 2 project
> 
> Thanks Emmanuel - comments below.
> 
> -----Original Message-----
> From: Emmanuel Venisse [mailto:emmanuel@venisse.net]
> Sent: Friday, January 27, 2006 9:37 AM
> To: continuum-users@maven.apache.org
> Subject: Re: multi-module maven 2 project
> 
> Johnson, Jonathan a écrit :
> 
>>I'm using maven 2.0.2, Continuum 1.0.2 and java 1.5.  My project is a 
>>multi-module that is laid out in the recommended maven 2 manner and is 
>>building my projects (phew).  I have a couple questions about my 
>>experiences so far.
>>
>> 
>>
>>1.	When I change some information in my parent pom.xml (such as the
>>developer list.)  do I have to readd the pom again.  Is there a 
>>refresh option?
> 
> 
>>>Normally, the pom will be refresh automatically by continuum, but it 
>>>
>>>>>>>doens't to do it. File an issue about it.
>>>
>>>So actually, if your pom isn't updated in continuum, delete your project
>>>and readd it.
> 
> 
> I will file the issue.
> 
> 
>>2.	If I add my parent pom.xsl it adds all the child modules again
>>and there are duplicate modules in the continuum projects list.  I 
>>then have to remove my old modules and readjust the local continuum 
>>settings such as the schedule and targets.  When I apply and updated 
>>pom, I wish it just updated them and kept my local continuum settings.
> 
> 
>>>File an issue, i'll look at it.
>>>Your modules was already in continuum before adding the parent, right?
> 
> 
> Yes.  The steps are add a parent pom.xml file.  Notice the parent and all
> submodules appear.  Not add a new version of the same parent pom.xml.  The
> sub-modules will appear twice in the list.
> 
> I will file the issue.
> 
> 
>>3.	Removing projects from continuum can take several minutes.  
> 
> 
>>>If your project is big, it can take several minutes because we clean 
>>>all >> infos in database and directories.
> 
> 
> The more classes in the module, the longer it takes, yet for a module with
> <1000 classes is takes several minutes. I will file the issue. 
> 
> 
>>4.	Adding project to continuum takes several minutes.
> 
> 
>>>Only if you have lot of modules.
> 
> 
>>5.	Is performance being addressed or am I doing something wrong?
>>I'm running red hat linux box with a decent processor.  My 
>>multi-module project only has about 1000 classes.  Its take me about 
>>15 minutes to update a pom.xml in continuum.
>>
> 
> 
>>>Is it 15 minutes to checkout/update from scm or to build the project?
> 
> 
> I takes about two minutes to do a CVS checkout of all the source.  Yes CVS
> is slow, but is seems continuum is taking much longer to do a multi-project
> add.  Once I have hard numbers I will file an issue.
> 
> Emmanuel
> 
> 
> LEGAL NOTICE:
> Unless expressly stated otherwise, this message is confidential and may be
> privileged. It is intended for the addressee(s) only. Access to this e-mail
> by anyone else is unauthorized. If you are not an addressee, any disclosure
> or copying of the contents or any action taken (or not taken) in reliance on
> it is unauthorized and may be unlawful. If you are not an addressee, please
> inform the sender immediately.
>  ------
> 
> 
> --------------------------------------------------------------------------------
> The information contained herein is confidential and is intended solely for the
> addressee. Access by any other party is unauthorised without the express 
> written permission of the sender. If you are not the intended recipient, please 
> contact the sender either via the company switchboard on +44 (0)20 7623 8000, or
> via e-mail return. If you have received this e-mail in error or wish to read our
> e-mail disclaimer statement and monitoring policy, please refer to 
> http://www.drkw.com/disc/email/ or contact the sender. 3166
> --------------------------------------------------------------------------------
> 
> 
> 
> 


Mime
View raw message