The vote has passed with the following result :
+3 (binding): Jason, Brian, John
+3 (non binding): Benjamen, Paul, Oleg
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.o
+1
-Original Message-
From: John Casey [mailto:jdca...@commonjava.org]
Sent: Friday, April 10, 2009 3:59 PM
To: Maven Developers List
Subject: Re: [VOTE] Release mercury-1.0-alpha-6
+1
I didn't see this vote at first because for some reason my email client
thought it was part o
My client (thunderbird) did the same thing. Maybe Oleg replied to one of the
messages in the previous vote thread and so kept some of the headers.
John Casey wrote:
+1
I didn't see this vote at first because for some reason my email client
thought it was part of the alpha-5 vote thread. Sorr
+1
I didn't see this vote at first because for some reason my email client
thought it was part of the alpha-5 vote thread. Sorry for taking so long
to vote.
-john
Oleg Gusakov wrote:
Hi,
Iterative alpha release. Major fixes:
- # of dependencies - less'n 64 were ordered correctly the rest u
Oleg Gusakov wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-002/
+1
Repeated runs of the ITs revealed some instabilities that I recorded in
MERCURY-112 and MERCURY-113 for future investigation.
Benjamin
--
Paul Gier wrote:
Ok, +1 for the release.
I'll take a look at the SatSolver interface. Will there eventually be
a way to load customizations using a build extension or something like
it?
As I said - SatSolver interface is work-in-progress, so don't hold your
breath :) The two missing pieces
Ok, +1 for the release.
I'll take a look at the SatSolver interface. Will there eventually be a way to
load customizations using a build extension or something like it?
Oleg Gusakov wrote:
Paul Gier wrote:
I have a few questions and then I will give my +1.
It looks like the ant tasks are
Paul Gier wrote:
I have a few questions and then I will give my +1.
It looks like the ant tasks are part of the tag [1], but they are
still marked as a snapshot version. Is the ant-tasks module not part
of the release?
mercury-ant-tasks happens to be located inside, it will go away as soon
I have a few questions and then I will give my +1.
It looks like the ant tasks are part of the tag [1], but they are still marked
as a snapshot version. Is the ant-tasks module not part of the release? Will
there be a separate release for this?
I also tried running a simple project using th
Excellent. +1 (non binding).
I have a related question: Can you guys also release
org.apache.maven:maven-mercury:jar:3.0-SNAPSHOT so we have a stable
artifacts to build against. Otherwise like in the mercury-1.0-alpha-5
release, the snapshot will (possibly) move forward and it will not be
useful an
+1
On 7-Apr-09, at 2:34 PM, Oleg Gusakov wrote:
Hi,
Iterative alpha release. Major fixes:
- # of dependencies - less'n 64 were ordered correctly the rest used
to be random ordering
- bad/missing repository metadata is worked around in most cases
Mercury-ant is now successfully used to boot
Hi,
Iterative alpha release. Major fixes:
- # of dependencies - less'n 64 were ordered correctly the rest used to
be random ordering
- bad/missing repository metadata is worked around in most cases
Mercury-ant is now successfully used to bootstrap build Maven3 trunk.
Working towards implement
12 matches
Mail list logo
