You are viewing a plain text version of this content. The canonical link for it is here.
Posted to announce@apache.org by Brett Porter <br...@apache.org> on 2004/12/07 13:56:37 UTC
[ANN] Maven 1.0.2 Released
The Apache Maven team is pleased to announce the Maven 1.0.2 release!
We recommend that all users upgrade to this release, in particular those
using pre-1.0 betas or release candidates.
http://maven.apache.org/start/download.html
Fixed bugs:
o Ensure that default properties (such as maven.repo.remote) are
correctly overidden when inherited from a parent. Issue: MAVEN-1501.
o Allow SNAPSHOT as a version override. Issue: MAVEN-1511.
o Prevent "Response Content Length not known" warning. Issue: MAVEN-1428.
o Fail on 403 HTTP response to dependency download. Issue: MAVEN-1502.
o Now works on IBM JDK 1.3. Issue: MAVEN-1507.
o Don't download a dependency if there is a JAR override for it. Issue:
MAVEN-1518. Thanks to Hardy Ferentschik.
o Works with JDK 1.5 without additional configuration.
-The Apache Maven team
Re: [ANN] Maven 1.0.2 Released
Posted by John Taylor <jd...@roe.ac.uk>.
My initial tests suggest that the multiproject/property inheritance problem
that has given me such headaches for 6 months has indeed been fixed. This
is going to make my life *so* much easier. Thanks guys - we really
appreciate your efforts,
John
=====================================
John Taylor
Astrogrid Java Developer
http://www.astrogrid.org/maven/docs/HEAD/
Royal Observatory of Edinburgh
http://www.roe.ac.uk/ifa/about/directory.html
+44 (0) 131 668 8329
skype id: johndavidtaylor
=====================================
> The Apache Maven team is pleased to announce the Maven 1.0.2 release!
>
> We recommend that all users upgrade to this release, in particular those
> using pre-1.0 betas or release candidates.
>
> http://maven.apache.org/start/download.html
>
> Fixed bugs:
> o Ensure that default properties (such as maven.repo.remote) are correctly
> overidden when inherited from a parent. Issue: MAVEN-1501.
> o Allow SNAPSHOT as a version override. Issue: MAVEN-1511.
> o Prevent "Response Content Length not known" warning. Issue: MAVEN-1428.
> o Fail on 403 HTTP response to dependency download. Issue: MAVEN-1502.
> o Now works on IBM JDK 1.3. Issue: MAVEN-1507.
> o Don't download a dependency if there is a JAR override for it. Issue:
> MAVEN-1518. Thanks to Hardy Ferentschik.
> o Works with JDK 1.5 without additional configuration.
>
> -The Apache Maven team
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: 1.0.2 startup slow
Posted by Charles Daniels <cj...@yahoo.com>.
Same here. Unpacking plugin jars every time. Startup time for me is
consistently 16 seconds.
> -----Original Message-----
> From: Joe Shomphe [mailto:jshomphe@gmail.com]
> Sent: Tuesday, December 07, 2004 10:40 AM
> To: Maven Users List
> Subject: Re: 1.0.2 startup slow
>
> Yeah, I am seeing the same thing here.
>
> Every time maven runs, it seems to be unpacking its jars to my local
> repo every time.
>
> I have tried removing my ~/.maven directory, but that didnt
> seem to work.
>
>
> Output from maven -X:
>
>
> Unpacking maven-announcement-plugin-1.3.jar to directory -->
> C:\Documents and
> Settings\joes\.maven\cache\maven-announcement-plugin-1.3
> Invalidating plugin maven-announcement-plugin-1.3
> removing dynataglib cache entry for uri announcement
> removing goal and plugin cache entry for goal announcement:generate
> removing goal and plugin cache entry for goal
> announcement:generate-all
> removing goal and plugin cache entry for goal announcement:mail
> removing goal and plugin cache entry for goal announcement:init
> removing goal and plugin cache entry for goal
> announcement:check-version
> removing goal and plugin cache entry for goal announcement
> removing dynatag dependency cache entry
> removing artifactId cache entry
>
>
>
>
> On Tue, 7 Dec 2004 10:28:23 -0700, Chad Brandon
> <ch...@yahoo.com> wrote:
> > Hi,
> >
> > First of all, great job on the 1.0.2 release! I just
> download the release
> > this morning and have been using it, and I've noticed the
> startup time has
> > dramatically increased. Startup time for just typing
> "maven" was between
> > 2-3 seconds on my machine for versions prior to 1.0.2, but
> 1.0.2 seems to
> > take around 25 seconds just to start up. Has anyone else
> noticed this? And
> > is there anything I can do to improve the time? I know
> about the maven
> > console plugin however I change directories a lot so it's
> not a great
> > alternative unless I just stay in the same directory the
> entire time.
> >
> > Thanks!
> >
> > Chad
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: 1.0.2 startup slow
Posted by Joe Shomphe <js...@gmail.com>.
Yeah, I am seeing the same thing here.
Every time maven runs, it seems to be unpacking its jars to my local
repo every time.
I have tried removing my ~/.maven directory, but that didnt seem to work.
Output from maven -X:
Unpacking maven-announcement-plugin-1.3.jar to directory -->
C:\Documents and
Settings\joes\.maven\cache\maven-announcement-plugin-1.3
Invalidating plugin maven-announcement-plugin-1.3
removing dynataglib cache entry for uri announcement
removing goal and plugin cache entry for goal announcement:generate
removing goal and plugin cache entry for goal announcement:generate-all
removing goal and plugin cache entry for goal announcement:mail
removing goal and plugin cache entry for goal announcement:init
removing goal and plugin cache entry for goal announcement:check-version
removing goal and plugin cache entry for goal announcement
removing dynatag dependency cache entry
removing artifactId cache entry
On Tue, 7 Dec 2004 10:28:23 -0700, Chad Brandon <ch...@yahoo.com> wrote:
> Hi,
>
> First of all, great job on the 1.0.2 release! I just download the release
> this morning and have been using it, and I've noticed the startup time has
> dramatically increased. Startup time for just typing "maven" was between
> 2-3 seconds on my machine for versions prior to 1.0.2, but 1.0.2 seems to
> take around 25 seconds just to start up. Has anyone else noticed this? And
> is there anything I can do to improve the time? I know about the maven
> console plugin however I change directories a lot so it's not a great
> alternative unless I just stay in the same directory the entire time.
>
> Thanks!
>
> Chad
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: 1.0.2 startup slow
Posted by Chad Brandon <ch...@yahoo.com>.
Yep! That was it...I just ran it this morning and all was fine :) I missed
the "PM" for the 10 when I looked at the timestamp yesterday of the plugins
within maven-1.0.2/plugins. Sorry about that, that would have answered the
question yesterday when you asked me to compare the timestamps!
Chad
-----Original Message-----
From: Brett Porter [mailto:brett.porter@gmail.com]
Sent: Wednesday, December 08, 2004 2:10 AM
To: Maven Users List
Subject: Re: 1.0.2 startup slow
How funny! Being in +11 at the moment, that certainly made it as bad
as it could be.
Thanks Leif!
Ok, I'll either set my clock back or build with significant lead time
in future...
Chad - can you confim it was the same for you?
Thanks,
Brett
On Wed, 08 Dec 2004 01:01:17 -0700, Leif Nelson <ln...@llnl.gov> wrote:
> I think I figured out what the problem is. When I did what you suggest
> (checkout the tagged version of maven, add logging, build and test) it
> works fine. 2 seconds on windows xp. So, on a hunch, I looked in the
> .zip file for maven-1.0.2.zip. And guess what, the date/time stamp of
> all the files in there is for 12/7/2004 at 10:13 PM. Well, us "early
> adopters" were running 1.0.2 before 10:13 PM on 12/7/04! The code in
> PluginManager.unpackPlugin() compares the date/time of the plugin.jar
> file with the date/time of the plugin cache dir. And of course, every
> time, it found that the jar was newer because it had a future date/time
> stamp, causing a cache invalidation for every invocation.
>
> So, for anyone who had this problem on 12/7, it will magically fix
> itself when their local time ticks past 10:13 PM. So, is the time wrong
> on the box that created the maven-1.0.2.zip file? Or, are zip files
> dumb enough to not contain a GMT offset? Who knows.
>
> Anyway, I'd bet the problem goes away now. I re-unzipped the
> distribution zip file, and since it's 12/8/04 12:58AM my time now, it
> takes 2 seconds to run maven on my windows box.
>
> Hope that helps,
> --Leif
>
>
>
> Brett Porter wrote:
>
> >Ok, this has got me stumped. I don't know what's different.
> >
> >Let me outline where we are at:
> >- first run is always slower
> >- second run should not unpack any plugins or touch the cache
> >- the reason that blowing away the cache is faster than running with
> >it when the unpacking is happening is because it is actually manually
> >erasing each, then recaching instead of just the last step, so that's
> >fine.
> >
> >We need to sort out what is triggering the unpacking.
> >
> >Is anyone experiencing this problem comfortable with building from tag
> >MAVEN-1_0_2, then adding debug statements to PluginManager.java and
> >recompiling?
> >If not, I can do this and provide a debugging maven.jar to try out...
> >
> >Can someone let me know (Chad?) when you are able to look at this, and
> >if possible jump onto irc.codehaus.org (you can get there by HTTP if
> >needed) so we can walk through it.
> >
> >Thanks,
> >Brett
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: 1.0.2 startup slow
Posted by Brett Porter <br...@gmail.com>.
How funny! Being in +11 at the moment, that certainly made it as bad
as it could be.
Thanks Leif!
Ok, I'll either set my clock back or build with significant lead time
in future...
Chad - can you confim it was the same for you?
Thanks,
Brett
On Wed, 08 Dec 2004 01:01:17 -0700, Leif Nelson <ln...@llnl.gov> wrote:
> I think I figured out what the problem is. When I did what you suggest
> (checkout the tagged version of maven, add logging, build and test) it
> works fine. 2 seconds on windows xp. So, on a hunch, I looked in the
> .zip file for maven-1.0.2.zip. And guess what, the date/time stamp of
> all the files in there is for 12/7/2004 at 10:13 PM. Well, us "early
> adopters" were running 1.0.2 before 10:13 PM on 12/7/04! The code in
> PluginManager.unpackPlugin() compares the date/time of the plugin.jar
> file with the date/time of the plugin cache dir. And of course, every
> time, it found that the jar was newer because it had a future date/time
> stamp, causing a cache invalidation for every invocation.
>
> So, for anyone who had this problem on 12/7, it will magically fix
> itself when their local time ticks past 10:13 PM. So, is the time wrong
> on the box that created the maven-1.0.2.zip file? Or, are zip files
> dumb enough to not contain a GMT offset? Who knows.
>
> Anyway, I'd bet the problem goes away now. I re-unzipped the
> distribution zip file, and since it's 12/8/04 12:58AM my time now, it
> takes 2 seconds to run maven on my windows box.
>
> Hope that helps,
> --Leif
>
>
>
> Brett Porter wrote:
>
> >Ok, this has got me stumped. I don't know what's different.
> >
> >Let me outline where we are at:
> >- first run is always slower
> >- second run should not unpack any plugins or touch the cache
> >- the reason that blowing away the cache is faster than running with
> >it when the unpacking is happening is because it is actually manually
> >erasing each, then recaching instead of just the last step, so that's
> >fine.
> >
> >We need to sort out what is triggering the unpacking.
> >
> >Is anyone experiencing this problem comfortable with building from tag
> >MAVEN-1_0_2, then adding debug statements to PluginManager.java and
> >recompiling?
> >If not, I can do this and provide a debugging maven.jar to try out...
> >
> >Can someone let me know (Chad?) when you are able to look at this, and
> >if possible jump onto irc.codehaus.org (you can get there by HTTP if
> >needed) so we can walk through it.
> >
> >Thanks,
> >Brett
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: 1.0.2 startup slow
Posted by Leif Nelson <ln...@llnl.gov>.
I think I figured out what the problem is. When I did what you suggest
(checkout the tagged version of maven, add logging, build and test) it
works fine. 2 seconds on windows xp. So, on a hunch, I looked in the
.zip file for maven-1.0.2.zip. And guess what, the date/time stamp of
all the files in there is for 12/7/2004 at 10:13 PM. Well, us "early
adopters" were running 1.0.2 before 10:13 PM on 12/7/04! The code in
PluginManager.unpackPlugin() compares the date/time of the plugin.jar
file with the date/time of the plugin cache dir. And of course, every
time, it found that the jar was newer because it had a future date/time
stamp, causing a cache invalidation for every invocation.
So, for anyone who had this problem on 12/7, it will magically fix
itself when their local time ticks past 10:13 PM. So, is the time wrong
on the box that created the maven-1.0.2.zip file? Or, are zip files
dumb enough to not contain a GMT offset? Who knows.
Anyway, I'd bet the problem goes away now. I re-unzipped the
distribution zip file, and since it's 12/8/04 12:58AM my time now, it
takes 2 seconds to run maven on my windows box.
Hope that helps,
--Leif
Brett Porter wrote:
>Ok, this has got me stumped. I don't know what's different.
>
>Let me outline where we are at:
>- first run is always slower
>- second run should not unpack any plugins or touch the cache
>- the reason that blowing away the cache is faster than running with
>it when the unpacking is happening is because it is actually manually
>erasing each, then recaching instead of just the last step, so that's
>fine.
>
>We need to sort out what is triggering the unpacking.
>
>Is anyone experiencing this problem comfortable with building from tag
>MAVEN-1_0_2, then adding debug statements to PluginManager.java and
>recompiling?
>If not, I can do this and provide a debugging maven.jar to try out...
>
>Can someone let me know (Chad?) when you are able to look at this, and
>if possible jump onto irc.codehaus.org (you can get there by HTTP if
>needed) so we can walk through it.
>
>Thanks,
>Brett
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: 1.0.2 startup slow
Posted by Brett Porter <br...@gmail.com>.
Ok, this has got me stumped. I don't know what's different.
Let me outline where we are at:
- first run is always slower
- second run should not unpack any plugins or touch the cache
- the reason that blowing away the cache is faster than running with
it when the unpacking is happening is because it is actually manually
erasing each, then recaching instead of just the last step, so that's
fine.
We need to sort out what is triggering the unpacking.
Is anyone experiencing this problem comfortable with building from tag
MAVEN-1_0_2, then adding debug statements to PluginManager.java and
recompiling?
If not, I can do this and provide a debugging maven.jar to try out...
Can someone let me know (Chad?) when you are able to look at this, and
if possible jump onto irc.codehaus.org (you can get there by HTTP if
needed) so we can walk through it.
Thanks,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
1.0.2 startup slow
Posted by Chad Brandon <ch...@yahoo.com>.
Hi,
First of all, great job on the 1.0.2 release! I just download the release
this morning and have been using it, and I've noticed the startup time has
dramatically increased. Startup time for just typing "maven" was between
2-3 seconds on my machine for versions prior to 1.0.2, but 1.0.2 seems to
take around 25 seconds just to start up. Has anyone else noticed this? And
is there anything I can do to improve the time? I know about the maven
console plugin however I change directories a lot so it's not a great
alternative unless I just stay in the same directory the entire time.
Thanks!
Chad
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org