RE: Project build order for multiple Maven 2 projects - Alphabetical by Project Name?
Continuum build all maven projects in the order oof the dependencies tree AND if dependencies between projects are circular, Continuum build projects in alphabetical order. I'm still not clear about this. We have 1 multiproject build (maven2). Over time I have added the 99 projects (a project per module) using the POM urls in several stages scattered over several project groups. All is fine, but now when I update the version of the modules in scm (eg release:prepare) things fall apart :( Does continuum only consider all projects that where added at one time? Does continuum only look at dependencies and not the parent? Does continuum not like the fact that I use multiple project groups for 1 multiproject build? regards, Bram ps. I use continuum-20070323.15 at this point -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: Monday, May 21, 2007 12:18 PM To: continuum-users@maven.apache.org Subject: Re: Project build order for multiple Maven 2 projects - Alphabetical by Project Name? Continuum build all maven projects in the order oof the dependencies tree AND if dependencies between projects are circular, Continuum build projects in alphabetical order. Continuum 1.0.3 build only dependecy that have some changes in SCM but not on dependency changes. You can try Continuum 1.1, if a new build of a module is done by continuum, Continuum will build dependent projects even if they don't have SCM changes. Emmanuel Shaun Barriball a écrit : Hi all, We've been using Continuum (1.0.3) successfully as part of our automated build and deploy for 6 months or so. We have one big issue which I'd appreciate input on. We have a large software system with 15 or so separate Maven 2 projects (assume for simplicity Project A, Project B and Project C) which each have sub-modules. Assume the dependency tree is: A - depends on C - depends on B (for example). These dependencies are expressed using Maven 2 dependency hierarchy. The Build All function on Continuum appears to ignore any Maven 2 dependency hierarchy and simply builds them in alphabetical order of the Project Name. This therefore builds the above example out of order - often resulting in build failures. * Should continuum 'understand' the dependency tree? I've read some material which implies this should potentially be the case (http://jira.codehaus.org/browse/CONTINUUM-39). * If not, is there a way to organise the build order for Build All above and beyond altering the project names with 1., 2. etc (which is obviously undesirable)? All help appreciated. Regards, Shaun.
RE: Project build order for multiple Maven 2 projects - Alphabetical by Project Name?
Hi Emmanual et al, After a few hours migrating our 15 plus projects to Continuum 1.1 we now have everything up and running. I've been impressed with 1.1 (great work). 2 issues thus far: Issue 1 - Do we delete Project sub-modules? Consider the scenario: Project Group MyBigProject Project A pom.xml Module 1 pom.xml Module 2 pom.xml Project B ... Project C * in Continuum 1.0.3 if you had a project of the above format when adding each Maven 2 project you would have to delete Module 1 and Module 2 to leave a single Project A. You then delete the -no-recurse option on the Maven build line so it builds the whole project. In Continuum 1.1 it uses the dependencies to determine the build order. Given that the root pom of each projects do not have any of their 'own' dependencies (they just define dependencies used by sub-modules) should we still be deleting Module 1, Module 2 etc? Issue 2 - Performance -- Out of the box Continuum 1.1 appears much, much slower than 1.0.3. For example, it takes 30 secs+ after I click MyBigProject to display the contents of the Project Group which has 10 Projects. Are there any logging settings/go faster buttons that would help improve performance? Regards, Shaun. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 21 May 2007 18:00 To: continuum-users@maven.apache.org Subject: Re: Project build order for multiple Maven 2 projects - Alphabetical by Project Name? You must readd all projects Emmanuel Shaun Barriball a écrit : We're just trying the upgrade to 1.1 now from 1.0.3. Is there an upgrade path for this which preserves the database or do we have to re-install all projects from scratch? 1.1 isn't mentioned on http://maven.apache.org/continuum/upgrade.html. Regards, Shaun. -Original Message- From: Jeffery, Mark [mailto:[EMAIL PROTECTED] Sent: 21 May 2007 11:38 To: continuum-users@maven.apache.org Subject: RE: Project build order for multiple Maven 2 projects - Alphabetical by Project Name? Yeah.I am battling with the same thing http://jira.codehaus.org/browse/CONTINUUM-998 Should be fixed in 1.1-alpha-# Jeff -Original Message- From: Shaun Barriball [mailto:[EMAIL PROTECTED] Sent: 21 May 2007 11:41 To: continuum-users@maven.apache.org Subject: Project build order for multiple Maven 2 projects - Alphabetical by Project Name? Hi all, We've been using Continuum (1.0.3) successfully as part of our automated build and deploy for 6 months or so. We have one big issue which I'd appreciate input on. We have a large software system with 15 or so separate Maven 2 projects (assume for simplicity Project A, Project B and Project C) which each have sub-modules. Assume the dependency tree is: A - depends on C - depends on B (for example). These dependencies are expressed using Maven 2 dependency hierarchy. The Build All function on Continuum appears to ignore any Maven 2 dependency hierarchy and simply builds them in alphabetical order of the Project Name. This therefore builds the above example out of order - often resulting in build failures. * Should continuum 'understand' the dependency tree? I've read some material which implies this should potentially be the case (http://jira.codehaus.org/browse/CONTINUUM-39). * If not, is there a way to organise the build order for Build All above and beyond altering the project names with 1., 2. etc (which is obviously undesirable)? All help appreciated. Regards, Shaun. To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer.
Re: Project build order for multiple Maven 2 projects - Alphabetical by Project Name?
On 21/05/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: You must readd all projects Is there no planned upgrade path from 1.0.3? We have 400+ projects in 1.0.3 and would like to upgrade to 1.1 - obviously this will take a few man years if done manually.. Cheers, Mark
Re: Project build order for multiple Maven 2 projects - Alphabetical by Project Name?
On 22/05/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: We'll probably do one but not for 1.1-alpha-* Okay cool, we'll wait until then thanks. Mark
Re: Project build order for multiple Maven 2 projects - Alphabetical by Project Name?
It's better to keep modules in continuum for build order resolution. Later, we'll add the possibility to add new dependencies on projects, so modules will can be removed. Emmanuel Shaun Barriball a écrit : Hi Emmanual et al, After a few hours migrating our 15 plus projects to Continuum 1.1 we now have everything up and running. I've been impressed with 1.1 (great work). 2 issues thus far: Issue 1 - Do we delete Project sub-modules? Consider the scenario: Project Group MyBigProject Project A pom.xml Module 1 pom.xml Module 2 pom.xml Project B ... Project C * in Continuum 1.0.3 if you had a project of the above format when adding each Maven 2 project you would have to delete Module 1 and Module 2 to leave a single Project A. You then delete the -no-recurse option on the Maven build line so it builds the whole project. In Continuum 1.1 it uses the dependencies to determine the build order. Given that the root pom of each projects do not have any of their 'own' dependencies (they just define dependencies used by sub-modules) should we still be deleting Module 1, Module 2 etc? Issue 2 - Performance -- Out of the box Continuum 1.1 appears much, much slower than 1.0.3. For example, it takes 30 secs+ after I click MyBigProject to display the contents of the Project Group which has 10 Projects. Are there any logging settings/go faster buttons that would help improve performance? Regards, Shaun. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 21 May 2007 18:00 To: continuum-users@maven.apache.org Subject: Re: Project build order for multiple Maven 2 projects - Alphabetical by Project Name? You must readd all projects Emmanuel Shaun Barriball a écrit : We're just trying the upgrade to 1.1 now from 1.0.3. Is there an upgrade path for this which preserves the database or do we have to re-install all projects from scratch? 1.1 isn't mentioned on http://maven.apache.org/continuum/upgrade.html. Regards, Shaun. -Original Message- From: Jeffery, Mark [mailto:[EMAIL PROTECTED] Sent: 21 May 2007 11:38 To: continuum-users@maven.apache.org Subject: RE: Project build order for multiple Maven 2 projects - Alphabetical by Project Name? Yeah.I am battling with the same thing http://jira.codehaus.org/browse/CONTINUUM-998 Should be fixed in 1.1-alpha-# Jeff -Original Message- From: Shaun Barriball [mailto:[EMAIL PROTECTED] Sent: 21 May 2007 11:41 To: continuum-users@maven.apache.org Subject: Project build order for multiple Maven 2 projects - Alphabetical by Project Name? Hi all, We've been using Continuum (1.0.3) successfully as part of our automated build and deploy for 6 months or so. We have one big issue which I'd appreciate input on. We have a large software system with 15 or so separate Maven 2 projects (assume for simplicity Project A, Project B and Project C) which each have sub-modules. Assume the dependency tree is: A - depends on C - depends on B (for example). These dependencies are expressed using Maven 2 dependency hierarchy. The Build All function on Continuum appears to ignore any Maven 2 dependency hierarchy and simply builds them in alphabetical order of the Project Name. This therefore builds the above example out of order - often resulting in build failures. * Should continuum 'understand' the dependency tree? I've read some material which implies this should potentially be the case (http://jira.codehaus.org/browse/CONTINUUM-39). * If not, is there a way to organise the build order for Build All above and beyond altering the project names with 1., 2. etc (which is obviously undesirable)? All help appreciated. Regards, Shaun. To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer.
Re: Project build order for multiple Maven 2 projects - Alphabetical by Project Name?
Continuum build all maven projects in the order oof the dependencies tree AND if dependencies between projects are circular, Continuum build projects in alphabetical order. Continuum 1.0.3 build only dependecy that have some changes in SCM but not on dependency changes. You can try Continuum 1.1, if a new build of a module is done by continuum, Continuum will build dependent projects even if they don't have SCM changes. Emmanuel Shaun Barriball a écrit : Hi all, We've been using Continuum (1.0.3) successfully as part of our automated build and deploy for 6 months or so. We have one big issue which I'd appreciate input on. We have a large software system with 15 or so separate Maven 2 projects (assume for simplicity Project A, Project B and Project C) which each have sub-modules. Assume the dependency tree is: A - depends on C - depends on B (for example). These dependencies are expressed using Maven 2 dependency hierarchy. The Build All function on Continuum appears to ignore any Maven 2 dependency hierarchy and simply builds them in alphabetical order of the Project Name. This therefore builds the above example out of order - often resulting in build failures. * Should continuum 'understand' the dependency tree? I've read some material which implies this should potentially be the case (http://jira.codehaus.org/browse/CONTINUUM-39). * If not, is there a way to organise the build order for Build All above and beyond altering the project names with 1., 2. etc (which is obviously undesirable)? All help appreciated. Regards, Shaun.
Re: Project build order
Sounds to me like Client depends on Server depends on Common. Thus: common/pom.xml dependencies...none.../dependencies server/pom.xml dependencies...common.../dependencies client/pom.xml dependencies...server, common.../dependencies or dependencies...server.../dependencies and common will be pulled in via transitive dependencies Is there a reason you can't set things up like this, or why this won't work for you? Wayne On 11/6/06, Petter Måhlén [EMAIL PROTECTED] wrote: Hi, I have a question concerning what I can do to force projects to be built in a specific order. There have been some previous similar queries, but they don't quite seem to apply to our situation. What we want is this: 1. 'mvn clean install' for project 'common': this leads to a jar file with common message definitions for node-node communication being updated. 2. 'mvn clean install' for project 'server': we have written a simple Maven plugin that reads the message definitions, and generates source code that parses/packages the messages. 3. 'ant clean test' for project 'client': this again generates source code for parsing/packaging messages, but this time for the client. Is it possible for us to specify this order somehow? As it is, the builds will more or less randomly fail depending on which order they are executed in. It may be relevant that the 'server-common' dependency is configured like so: project ... build plugins plugin groupIdse.jadestone.whine/groupId artifactIdmaven-whine-generator/artifactId version3.0/version ... dependencies dependency groupIdse.jadestone.esports/groupId artifactIdhc-common/artifactId version0.0.1/version /dependency /dependencies /plugin ... The 'common' jar must be available on the classpath of the plugin that generates source code, and like this, it is only available at that point, which is great since we don't want to include it in the shipped product. Thanks for any help, Petter Cell: +46 704 40 30 25 Direct: +46 8 442 75 95 Fax: +46 8 24 05 08 www.jadestone.se Björns Trädgårdsgränd 1, 116 21 Stockholm, Sweden
