Re: possible performance bottleneck in current trunk

2007-12-22 Thread Jason van Zyl
On 22 Dec 07, at 9:55 AM 22 Dec 07, Ralph Goers wrote: If I can get some time I might look at it as well. This wouldn't necessarily be a bad thing if it can tell you all of the errors after preparing the projects. There are probably things we can know before project collection, like li

Re: possible performance bottleneck in current trunk

2007-12-22 Thread Jason van Zyl
On 22 Dec 07, at 9:09 AM 22 Dec 07, Milos Kleint wrote: On Dec 22, 2007 5:17 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote: On 22 Dec 07, at 1:02 AM 22 Dec 07, Milos Kleint wrote: i've played with the DefaultLifecycleExecutor and DefaultPluginManager a bit and tried to separate the preparati

Re: possible performance bottleneck in current trunk

2007-12-22 Thread Ralph Goers
If I can get some time I might look at it as well. This wouldn't necessarily be a bad thing if it can tell you all of the errors after preparing the projects. Milos Kleint wrote: The build doesn't fail fast now in some cases. It will prepare all the 20 project's lifecycles, perform dependency

Re: possible performance bottleneck in current trunk

2007-12-22 Thread Milos Kleint
On Dec 22, 2007 5:17 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > On 22 Dec 07, at 1:02 AM 22 Dec 07, Milos Kleint wrote: > > > i've played with the DefaultLifecycleExecutor and > > DefaultPluginManager a bit and tried to separate the preparation > > phase from the actual mojo executions. The

Re: possible performance bottleneck in current trunk

2007-12-22 Thread Jason van Zyl
On 22 Dec 07, at 1:02 AM 22 Dec 07, Milos Kleint wrote: i've played with the DefaultLifecycleExecutor and DefaultPluginManager a bit and tried to separate the preparation phase from the actual mojo executions. The preparations seem to attribute to astonishing 90% of the build execution. Se

Re: possible performance bottleneck in current trunk

2007-12-22 Thread Milos Kleint
i've played with the DefaultLifecycleExecutor and DefaultPluginManager a bit and tried to separate the preparation phase from the actual mojo executions. The preparations seem to attribute to astonishing 90% of the build execution. See http://picasaweb.google.com/mkleint/Maven/photo#514652046395121

Re: possible performance bottleneck in current trunk

2007-12-19 Thread Jason van Zyl
On 19 Dec 07, at 12:28 PM 19 Dec 07, Milos Kleint wrote: here is the actual screenshot. http://picasaweb.google.com/mkleint/Maven more inline.. On Dec 19, 2007 9:19 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote: On 19 Dec 07, at 11:10 AM 19 Dec 07, Milos Kleint wrote: Hello, i've started

Re: possible performance bottleneck in current trunk

2007-12-19 Thread Milos Kleint
here is the actual screenshot. http://picasaweb.google.com/mkleint/Maven more inline.. On Dec 19, 2007 9:19 PM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > On 19 Dec 07, at 11:10 AM 19 Dec 07, Milos Kleint wrote: > > > Hello, > > > > i've started building my project with current 2.1-SNAPSHOT t

RE: possible performance bottleneck in current trunk

2007-12-19 Thread Brian E. Fox
eclare the scope they want will work in some situations. -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 19, 2007 3:19 PM To: Maven Developers List Subject: Re: possible performance bottleneck in current trunk On 19 Dec 07, at 11:10 AM 19 Dec

Re: possible performance bottleneck in current trunk

2007-12-19 Thread Jason van Zyl
On 19 Dec 07, at 11:10 AM 19 Dec 07, Milos Kleint wrote: Hello, i've started building my project with current 2.1-SNAPSHOT trunk and I noticed the build is taking more time than before. I did a bit of profiling. I've executed "mvn install" on a set of 24 projects, all build before, right

Re: possible performance bottleneck in current trunk

2007-12-19 Thread Jerome Lacoste
On Dec 19, 2007 8:10 PM, Milos Kleint <[EMAIL PROTECTED]> wrote: > Hello, > > i've started building my project with current 2.1-SNAPSHOT trunk and I > noticed the build is taking more time than before. I did a bit of profiling. > I've executed "mvn install" on a set of 24 projects, all build before