, and here is yet another release candidate.
You can get RC8 here:
http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC8/org/apache/maven/apache-maven/2.0.10-RC8
Thanks for your patience during this release process. I know it's drawn
out and getting a little old, but we're getting
I reopen MRELEASE-3, this is a regression probably back at maven
2.0.6, and hope it can be squeezed to 2.0.10
Thanks
-D
On Fri, Aug 15, 2008 at 9:03 AM, John Casey [EMAIL PROTECTED] wrote:
I opened MNG-3718 for this (I probably didn't need to, but there ya go...)
And, it's fixed in SVN. I'll
i think the fix was in the core
On Sat, Aug 16, 2008 at 1:03 PM, Dan Tran [EMAIL PROTECTED] wrote:
I reopen MRELEASE-3, this is a regression probably back at maven
2.0.6, and hope it can be squeezed to 2.0.10
Thanks
-D
On Fri, Aug 15, 2008 at 9:03 AM, John Casey [EMAIL PROTECTED] wrote:
Developers List
Subject: Re: Maven 2.0.10-RC8
I reopen MRELEASE-3, this is a regression probably back at maven
2.0.6, and hope it can be squeezed to 2.0.10
Thanks
-D
On Fri, Aug 15, 2008 at 9:03 AM, John Casey [EMAIL PROTECTED]
wrote:
I opened MNG-3718 for this (I probably didn't need to, but there ya
On Fri, Aug 15, 2008 at 6:28 AM, John Casey [EMAIL PROTECTED] wrote:
As you've undoubtedly noticed, the RC7 distro didn't last very long before a
nasty bug showed up...actually two, but they were related.
John, you've got my admiration for your patience!
--
Look, that's why there's rules,
Le vendredi 15 août 2008, Jochen Wiedmann a écrit :
On Fri, Aug 15, 2008 at 6:28 AM, John Casey [EMAIL PROTECTED] wrote:
As you've undoubtedly noticed, the RC7 distro didn't last very long
before a nasty bug showed up...actually two, but they were related.
John, you've got my admiration for
-maven/2.0.10-RC8/org/apache/maven/apache-maven/2.0.10-RC8
Thanks for your patience during this release process. I know it's
drawn out and getting a little old, but we're getting there. The
bottom line is: we need many, many more integration tests to shorten
this process. For now, all we can do
More than anything else, I just hope that I don't wear out the patience
of the dev community in testing RC after RC...this is a sort of burn
in process for Maven 2.0.10, but I'm starting to wonder if it's also a
burn out period for Maven devs. :-)
-j
Jochen Wiedmann wrote:
On Fri, Aug 15,
I opened MNG-3718 for this (I probably didn't need to, but there ya go...)
And, it's fixed in SVN. I'll wait a bit to see if anything more serious
pops up for RC8 (other than Brett's change) before I respin RC9.
-john
Paul Benedict wrote:
I think I found bug in regards to MNG-2562. I tried
/2.0.10-RC8/org/apache/maven/apache-maven/2.0.10-RC8
Thanks for your patience during this release process. I know it's drawn
out and getting a little old, but we're getting there. The bottom line
is: we need many, many more integration tests to shorten this process.
For now, all we can do is add use
On 15/08/2008, at 2:28 PM, John Casey wrote:
Thanks for your patience during this release process. I know it's
drawn out and getting a little old, but we're getting there. The
bottom line is: we need many, many more integration tests to shorten
this process. For now, all we can do is add
I think I found bug in regards to MNG-2562. I tried out the new
${build.timestamp} and noticed that the timestamp was wrong. My local
time is 12:30 AM (30 minutes after midnight), but the value comes out
as 20080815-1230. That means timestamps are not unique. Any value in
the AM hour will be
12 matches
Mail list logo
