[Engine-devel] Maven 3 here we come!
Hi all, As discussed last month[1], we had to deal with some issues which turned out to be a Maven bug. Thanks to Juan and Asaf's work, our current sources now build properly using Maven 3. So you're all invited to migrate into Maven 3. Other than upgrading your local maven package no other action is needed. For now, Maven 2 will also work for you, but I expect in the future we'd like to make use of some advanced features, so migration to 3 is recommended. Talking about advanced features, an interesting challenge is feedback on parallel builds [2]. So whoever wants to try it out and report if it improves run time without breaking anything, will be appreciated. Happy migration! [1]http://lists.ovirt.org/pipermail/arch/2012-April/000490.html [2] https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html -- /d "Email returned to sender -- insufficient voltage."
----- Original Message -----
From: "Doron Fediuck" <dfediuck@redhat.com> To: engine-devel@ovirt.org Cc: "<arch@ovirt.org>" <arch@ovirt.org> Sent: Wednesday, May 23, 2012 12:59:53 PM Subject: [Engine-devel] Maven 3 here we come!
Hi all, As discussed last month[1], we had to deal with some issues which turned out to be a Maven bug. Thanks to Juan and Asaf's work, our current sources now build properly using Maven 3. So you're all invited to migrate into Maven 3. Other than upgrading your local maven package no other action is needed.
For now, Maven 2 will also work for you, but I expect in the future we'd like to make use of some advanced features, so migration to 3 is recommended.
Talking about advanced features, an interesting challenge is feedback on parallel builds [2]. So whoever wants to try it out and report if it improves run time without breaking anything, will be appreciated.
Happy migration!
[1]http://lists.ovirt.org/pipermail/arch/2012-April/000490.html [2] https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html --
+1 on the move and testing out new features!
/d
"Email returned to sender -- insufficient voltage." _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
New to maven. Using rhel6.2, and installed maven 3.0.4. Changed path to pick this version instead of 2.2.1 I was using before. when running "mvn clean install" I see - Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-install-plugin/... It doesn't look right, shouldn't it be maven3 instead of maven2 ? Do we need to update the "Maven personal settings" section on http://www.ovirt.org/wiki/Building_Ovirt_Engine At least the part where it says "maven 3.x will not work". How about ~/.m2/settings.xml ? -Sharad Quoting Eyal Edri <eedri@redhat.com>:
----- Original Message -----
From: "Doron Fediuck" <dfediuck@redhat.com> To: engine-devel@ovirt.org Cc: "<arch@ovirt.org>" <arch@ovirt.org> Sent: Wednesday, May 23, 2012 12:59:53 PM Subject: [Engine-devel] Maven 3 here we come!
Hi all, As discussed last month[1], we had to deal with some issues which turned out to be a Maven bug. Thanks to Juan and Asaf's work, our current sources now build properly using Maven 3. So you're all invited to migrate into Maven 3. Other than upgrading your local maven package no other action is needed.
For now, Maven 2 will also work for you, but I expect in the future we'd like to make use of some advanced features, so migration to 3 is recommended.
Talking about advanced features, an interesting challenge is feedback on parallel builds [2]. So whoever wants to try it out and report if it improves run time without breaking anything, will be appreciated.
Happy migration!
[1]http://lists.ovirt.org/pipermail/arch/2012-April/000490.html [2] https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html --
+1 on the move and testing out new features!
/d
"Email returned to sender -- insufficient voltage." _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
On 23/05/12 19:58, snmishra@linux.vnet.ibm.com wrote:
New to maven. Using rhel6.2, and installed maven 3.0.4. Changed path to pick this version instead of 2.2.1 I was using before.
when running "mvn clean install" I see -
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-install-plugin/...
It doesn't look right, shouldn't it be maven3 instead of maven2 ?
Sharad, Maven works with plugins for various tasks. Each plugin is a Maven artifact with its own version. The install plugin handles installation tasks to local repository. You can read more about it here: http://maven.apache.org/plugins/maven-install-plugin/ So in this case, your Maven 3 is using a plugin called maven-install, and the /plugin's/ version is 2.3.1. That's perfectly fine.
Do we need to update the "Maven personal settings" section on http://www.ovirt.org/wiki/Building_Ovirt_Engine
At least the part where it says "maven 3.x will not work". How about ~/.m2/settings.xml ?
Thanks for the reminder- wiki updated. No change needed for the settings.xml file, or its location.
-Sharad
Quoting Eyal Edri <eedri@redhat.com>:
----- Original Message -----
From: "Doron Fediuck" <dfediuck@redhat.com> To: engine-devel@ovirt.org Cc: "<arch@ovirt.org>" <arch@ovirt.org> Sent: Wednesday, May 23, 2012 12:59:53 PM Subject: [Engine-devel] Maven 3 here we come!
Hi all, As discussed last month[1], we had to deal with some issues which turned out to be a Maven bug. Thanks to Juan and Asaf's work, our current sources now build properly using Maven 3. So you're all invited to migrate into Maven 3. Other than upgrading your local maven package no other action is needed.
For now, Maven 2 will also work for you, but I expect in the future we'd like to make use of some advanced features, so migration to 3 is recommended.
Talking about advanced features, an interesting challenge is feedback on parallel builds [2]. So whoever wants to try it out and report if it improves run time without breaking anything, will be appreciated.
Happy migration!
[1]http://lists.ovirt.org/pipermail/arch/2012-April/000490.html [2] https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html --
+1 on the move and testing out new features!
/d
"Email returned to sender -- insufficient voltage." _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
-- /d "This message is made with 100% recycled electrons. No new atoms were destroyed in the making of this message."
On 05/23/2012 12:59 PM, Doron Fediuck wrote:
Hi all, As discussed last month[1], we had to deal with some issues which turned out to be a Maven bug. Thanks to Juan and Asaf's work, our current sources now build properly using Maven 3. So you're all invited to migrate into Maven 3. Other than upgrading your local maven package no other action is needed.
For now, Maven 2 will also work for you, but I expect in the future we'd like to make use of some advanced features, so migration to 3 is recommended.
Talking about advanced features, an interesting challenge is feedback on parallel builds [2].
I'm not happy with parallel builds - it creates more java processes, each taking quite a bit of memory. This, in turn, causes them to swap, making everything crawl. Took me 22 minutes to compile the webadmin and additional 21 minutes for the user portal, with -T 4. I've had 3.5GB of swap used (and 7GB resident memory with 'java' processes running around). It usually takes me The command line I've used was: mvn -T 4 clean install -Pgwt-admin,gwt-user -DskipTests=true -Dmaven.test.skip=true As opposed to 7+ 3 minutes without '-T 4'. Y.
So whoever wants to try it out and report if it improves run time without breaking anything, will be appreciated.
Happy migration!
[1]http://lists.ovirt.org/pipermail/arch/2012-April/000490.html [2]https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html
----- Original Message -----
From: "Yaniv Kaul" <ykaul@redhat.com> To: "Doron Fediuck" <dfediuck@redhat.com> Cc: engine-devel@ovirt.org, "<arch@ovirt.org>" <arch@ovirt.org> Sent: Wednesday, May 23, 2012 11:04:12 PM Subject: Re: [Engine-devel] Maven 3 here we come!
On 05/23/2012 12:59 PM, Doron Fediuck wrote:
Hi all, As discussed last month[1], we had to deal with some issues which turned out to be a Maven bug. Thanks to Juan and Asaf's work, our current sources now build properly using Maven 3. So you're all invited to migrate into Maven 3. Other than upgrading your local maven package no other action is needed.
For now, Maven 2 will also work for you, but I expect in the future we'd like to make use of some advanced features, so migration to 3 is recommended.
Talking about advanced features, an interesting challenge is feedback on parallel builds [2].
I'm not happy with parallel builds - it creates more java processes, each taking quite a bit of memory. This, in turn, causes them to swap, making everything crawl. Took me 22 minutes to compile the webadmin and additional 21 minutes for the user portal, with -T 4. I've had 3.5GB of swap used (and 7GB resident memory with 'java' processes running around). It usually takes me
The command line I've used was: mvn -T 4 clean install -Pgwt-admin,gwt-user -DskipTests=true -Dmaven.test.skip=true
Have you tried using the mvn -T 1C option (to run one thread per core?) On some builds it reduced my compilation time in a few min, but it wasn't consistent. also, maven says that some of the modules are not thread-safe and he will run then sequentially, so perhaps if the modules were re-factored to fit parallel builds, only then we'll see real improvement.
As opposed to 7+ 3 minutes without '-T 4'.
Y.
So whoever wants to try it out and report if it improves run time without breaking anything, will be appreciated.
Happy migration!
[1]http://lists.ovirt.org/pipermail/arch/2012-April/000490.html [2]https://cwiki.apache.org/MAVEN/parallel-builds-in-maven-3.html
_______________________________________________ Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch
On 05/23/2012 11:04 PM, Yaniv Kaul wrote:
On 05/23/2012 12:59 PM, Doron Fediuck wrote:
Hi all, As discussed last month[1], we had to deal with some issues which turned out to be a Maven bug. Thanks to Juan and Asaf's work, our current sources now build properly using Maven 3. So you're all invited to migrate into Maven 3. Other than upgrading your local maven package no other action is needed.
For now, Maven 2 will also work for you, but I expect in the future we'd like to make use of some advanced features, so migration to 3 is recommended.
Talking about advanced features, an interesting challenge is feedback on parallel builds [2].
I'm not happy with parallel builds - it creates more java processes, each taking quite a bit of memory. This, in turn, causes them to swap, making everything crawl. Took me 22 minutes to compile the webadmin and additional 21 minutes for the user portal, with -T 4. I've had 3.5GB of swap used (and 7GB resident memory with 'java' processes running around). It usually takes me
The command line I've used was: mvn -T 4 clean install -Pgwt-admin,gwt-user -DskipTests=true -Dmaven.test.skip=true
As opposed to 7+ 3 minutes without '-T 4'.
Saggi gave me his command line, which doesn't require any change of settings.xml mvn clean install -Pgwtdev,gwt-admin -DskipTests -Dgwt.userAgent=gecko1_8 -Dgwt.draftCompile=true -Dgwt.compiler.optimizationLevel=0 -Dgwt.compiler.localWorkers=2 -Dmaven.aspectj.incremental=true -Dmaven.aspectj.time=true I wonder if we shouldn't make something similar to this as the default. preferably, add ./configure script to tweak different options (which is very common in non java projects).
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Yaniv Kaul" <ykaul@redhat.com> Cc: engine-devel@ovirt.org, "<arch@ovirt.org>" <arch@ovirt.org> Sent: Friday, June 1, 2012 12:02:51 PM Subject: [Engine-devel] compile time (was Re: Maven 3 here we come!)
On 05/23/2012 11:04 PM, Yaniv Kaul wrote:
On 05/23/2012 12:59 PM, Doron Fediuck wrote:
Hi all, As discussed last month[1], we had to deal with some issues which turned out to be a Maven bug. Thanks to Juan and Asaf's work, our current sources now build properly using Maven 3. So you're all invited to migrate into Maven 3. Other than upgrading your local maven package no other action is needed.
For now, Maven 2 will also work for you, but I expect in the future we'd like to make use of some advanced features, so migration to 3 is recommended.
Talking about advanced features, an interesting challenge is feedback on parallel builds [2].
I'm not happy with parallel builds - it creates more java processes, each taking quite a bit of memory. This, in turn, causes them to swap, making everything crawl. Took me 22 minutes to compile the webadmin and additional 21 minutes for the user portal, with -T 4. I've had 3.5GB of swap used (and 7GB resident memory with 'java' processes running around). It usually takes me
The command line I've used was: mvn -T 4 clean install -Pgwt-admin,gwt-user -DskipTests=true -Dmaven.test.skip=true
As opposed to 7+ 3 minutes without '-T 4'.
Saggi gave me his command line, which doesn't require any change of settings.xml
mvn clean install -Pgwtdev,gwt-admin -DskipTests -Dgwt.userAgent=gecko1_8 -Dgwt.draftCompile=true -Dgwt.compiler.optimizationLevel=0 -Dgwt.compiler.localWorkers=2 -Dmaven.aspectj.incremental=true -Dmaven.aspectj.time=true It will have to be optional with configure flags like --disable-optimization --disable-extra-user-agents --local-workers=2 So people know what they are doing and can choose what is best for them as I use 2 local workers because my host as 2 cores with HT which means by default it will start 4 local workers and have all my processing threads stuck on IO stopping the machine. Other, more powerful hosts, might be able to ramp the local workers. Also you might want to turn on debug but still check other user agents.
I wonder if we shouldn't make something similar to this as the default. preferably, add ./configure script to tweak different options (which is very common in non java projects). _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
----- Original Message -----
From: "Itamar Heim" <iheim@redhat.com> To: "Yaniv Kaul" <ykaul@redhat.com> Cc: engine-devel@ovirt.org, "<arch@ovirt.org>" <arch@ovirt.org> Sent: Friday, June 1, 2012 7:02:51 PM Subject: compile time (was Re: [Engine-devel] Maven 3 here we come!)
On 05/23/2012 11:04 PM, Yaniv Kaul wrote:
On 05/23/2012 12:59 PM, Doron Fediuck wrote:
Hi all, As discussed last month[1], we had to deal with some issues which turned out to be a Maven bug. Thanks to Juan and Asaf's work, our current sources now build properly using Maven 3. So you're all invited to migrate into Maven 3. Other than upgrading your local maven package no other action is needed.
For now, Maven 2 will also work for you, but I expect in the future we'd like to make use of some advanced features, so migration to 3 is recommended.
Talking about advanced features, an interesting challenge is feedback on parallel builds [2].
I'm not happy with parallel builds - it creates more java processes, each taking quite a bit of memory. This, in turn, causes them to swap, making everything crawl. Took me 22 minutes to compile the webadmin and additional 21 minutes for the user portal, with -T 4. I've had 3.5GB of swap used (and 7GB resident memory with 'java' processes running around). It usually takes me
The command line I've used was: mvn -T 4 clean install -Pgwt-admin,gwt-user -DskipTests=true -Dmaven.test.skip=true
As opposed to 7+ 3 minutes without '-T 4'.
Saggi gave me his command line, which doesn't require any change of settings.xml
mvn clean install -Pgwtdev,gwt-admin -DskipTests -Dgwt.userAgent=gecko1_8 -Dgwt.draftCompile=true -Dgwt.compiler.optimizationLevel=0 -Dgwt.compiler.localWorkers=2 -Dmaven.aspectj.incremental=true -Dmaven.aspectj.time=true
how much time this command cuts from build time? shouldn't we use this in CI as well?
I wonder if we shouldn't make something similar to this as the default. preferably, add ./configure script to tweak different options (which is very common in non java projects). _______________________________________________ Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch
On 06/02/2012 12:00 PM, Eyal Edri wrote:
----- Original Message -----
From: "Itamar Heim"<iheim@redhat.com> To: "Yaniv Kaul"<ykaul@redhat.com> Cc: engine-devel@ovirt.org, "<arch@ovirt.org>"<arch@ovirt.org> Sent: Friday, June 1, 2012 7:02:51 PM Subject: compile time (was Re: [Engine-devel] Maven 3 here we come!)
On 05/23/2012 11:04 PM, Yaniv Kaul wrote:
On 05/23/2012 12:59 PM, Doron Fediuck wrote:
Hi all, As discussed last month[1], we had to deal with some issues which turned out to be a Maven bug. Thanks to Juan and Asaf's work, our current sources now build properly using Maven 3. So you're all invited to migrate into Maven 3. Other than upgrading your local maven package no other action is needed.
For now, Maven 2 will also work for you, but I expect in the future we'd like to make use of some advanced features, so migration to 3 is recommended.
Talking about advanced features, an interesting challenge is feedback on parallel builds [2].
I'm not happy with parallel builds - it creates more java processes, each taking quite a bit of memory. This, in turn, causes them to swap, making everything crawl. Took me 22 minutes to compile the webadmin and additional 21 minutes for the user portal, with -T 4. I've had 3.5GB of swap used (and 7GB resident memory with 'java' processes running around). It usually takes me
The command line I've used was: mvn -T 4 clean install -Pgwt-admin,gwt-user -DskipTests=true -Dmaven.test.skip=true
As opposed to 7+ 3 minutes without '-T 4'.
Saggi gave me his command line, which doesn't require any change of settings.xml
mvn clean install -Pgwtdev,gwt-admin -DskipTests -Dgwt.userAgent=gecko1_8 -Dgwt.draftCompile=true -Dgwt.compiler.optimizationLevel=0 -Dgwt.compiler.localWorkers=2 -Dmaven.aspectj.incremental=true -Dmaven.aspectj.time=true
how much time this command cuts from build time? shouldn't we use this in CI as well?
i get a 3.5 minutes build with this. with the exception of skipTests which in some jobs you want to run - yes. also -Pgwt-user is relevant to some jobs. (and if this becomes more of the default compile mode, you would need to tweak it only when you need to)
I wonder if we shouldn't make something similar to this as the default. preferably, add ./configure script to tweak different options (which is very common in non java projects). _______________________________________________ Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch
participants (6)
-
Doron Fediuck -
Eyal Edri -
Itamar Heim -
Saggi Mizrahi -
snmishraï¼ linux.vnet.ibm.com -
Yaniv Kaul