Nope, it was a bug in the 3599 test that caused it to serve up a test
pom for the wagon beta-3 but was only noticeable if you didn't already
have wagon-beta-3 in your local repo.
The bootstrap stuff John did is an attempt to put the maven build and
the its into a single execution. Jason should be
What was the problem? Just related to the bootstrap fixes John put in
place?
(Need to be merged to 2.1.x too, btw :)
Cheers,
Brett
On 30/10/2008, at 8:34 AM, Brian E. Fox wrote:
Ok, it's sorted out now and I'll stage RC2
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTE
The latest batch of issues are resolved and Its are passing.
Here's the list of issues fixed in 2.0.10:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112&styleName
=Html&projectId=10500&Create=Create
And I've staged RC-1 here:
http://people.apache.org/~brianf/staging-reposito
Ok, it's sorted out now and I'll stage RC2
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 4:41 PM
To: Maven Developers List
Subject: RE: [RC] Moving forward with 2.0.10
The 3599 tests are failing on the grid on all the vms it seems and o
The 3599 tests are failing on the grid on all the vms it seems and on my
machine. 3485 is also failing on windows in the grid.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 29, 2008 7:05 AM
To: Maven Developers List
Subject: Re: [RC] Moving for
We'll fix it in few hours.
I commited by error the main pom where I added the sample and the archetype
in the build
On Wed, Oct 29, 2008 at 6:05 PM, Hudson <[EMAIL PROTECTED]> wrote:
> See http://ci.sonatype.org/job/maven-core-integration-testing/227/changes
>
> Changes:
>
> [Arnaud HERITIER] Upd
Huh? The last attempt at 2.0.10 was months ago and this one was just
sitting around doing nothing ever since. The bandwagon gets too full
whenever it's release time and nothing happens in between, which is why
we introduced the process for the RC.
-Original Message-
From: Arnaud HERITIER
ok, thanks for those informations
Arnaud
On Wed, Oct 29, 2008 at 3:08 PM, Brian E. Fox <[EMAIL PROTECTED]>wrote:
> Hi Arnaud, Grid.sonatype.org/ci will replace the ci.sonatype.org. The
> jobs disabled on ci should be running on grid. Also, we ported the user
> credentials so if you could login t
I agree but I find the first RC was out quickly without giving the time to
review the bugs we wanted to fix in this version.
It's not a big problem. We'll fix it in the .11. I'm preparing an IT.
Arnaud
On Wed, Oct 29, 2008 at 2:47 PM, Brian Fox <[EMAIL PROTECTED]> wrote:
> Arnaud, the idea is to
Hi Arnaud, Grid.sonatype.org/ci will replace the ci.sonatype.org. The
jobs disabled on ci should be running on grid. Also, we ported the user
credentials so if you could login to ci previously, you can access the
grid instance also. I think everything except the m2e and tycho builds
are running on
You can't unset something like that because it appears null and the
merge will overwrite it. You could change it to something else though
--Brian (mobile)
On Oct 29, 2008, at 1:49 AM, Nick Pellow <[EMAIL PROTECTED]> wrote:
Hi,
If a plugin is defined in the normal build section of a pom and
Arnaud, the idea is to limit the scope to new regressions once we
start an RC. Otherwise we would spin in circles forever.
--Brian (mobile)
On Oct 29, 2008, at 2:04 AM, "Arnaud HERITIER" <[EMAIL PROTECTED]>
wrote:
ok brett,
I'll try to create a testcase without seam.
Even if we try to
Dear All,
What is your opinion about where is the best place to post a question about
Maven embedded?
Thanks and regards Carlos.
I checked these over and agree, they look good, and all the ITs pass,
so I went ahead and applied them. Thanks for figuring out the 3599
inconsistency :)
Cheers,
Brett
On 29/10/2008, at 3:42 AM, Benjamin Bentmann wrote:
Brian E. Fox wrote:
Please try it out and see if we have any remaini
Hi Guys,
I saw that there is now https://grid.sonatype.org/ci/ and
https://ci.sonatype.org/
There are some projects deactivated on them but we don't know why.
Can you try to add a note in the project description when you deactivate a
build to explain why.
Thanks
Cheers
--
..
Yep, re-applied it on 2.0.x / 2.0.10-RC.
On 29/10/2008, at 6:19 AM, John Casey wrote:
I seem to remember a fix brett put in for this when we were working
on [what became] 2.1.0-M1. I think it's in a console resolution
listener, possibly in maven-core or maven-artifact (-manager).
I'm prett
Sure, just that the final release still needs to be rolled from one or
the other, and wasn't sure which you were using. I was mostly asking
in the context of MNG-3599 that Benjamin pointed out to me on IRC
yesterday.
Since the 2.0.x is already rolled over to 2.0.11, I created a branch
2.0
17 matches
Mail list logo
