Artifacts have been pushed to Maven Central. I'll wait for them to arrive
before announcing and publishing the main site.
On Feb 20, 2014, at 3:22 AM, Olivier Lamy wrote:
> +1
> finally it's agile @apache :P
>
>
> On 20 February 2014 13:30, Igor Fedorenko wrote:
>> Jason, Stephen, other PMC
I'm spending some time trying to automate the last steps of the release so it's
not so tedious for anyone else who tries to do it. Dealing with the site and
putting binaries in SVN is not fun.
On Feb 20, 2014, at 12:02 PM, Mark Derricutt wrote:
> w00t ;-)
>
> Congrats on a fairly speedy relea
w00t ;-)
Congrats on a fairly speedy release! Roll on this new Maven Lifecycle
we have going on!
Mark
On 21 Feb 2014, at 3:54, Jason van Zyl wrote:
I will writeup the release notes, get the site published and promote
to Maven Central.
-
Hi,
The vote has passed with the following result:
+1 (binding): Jason van Zyl, Stephen Connolly, Arnaud Hértier, Olivier Lamy
+1 (non-binding): Manfred Moser, Igor Fedorenko, Karl Heinz Marbaise, Paul
Benedict, Mark Derricutt, Baptiste Mathus, Mirko Friedenhagen
I will writeup the release note
+1
finally it's agile @apache :P
On 20 February 2014 13:30, Igor Fedorenko wrote:
> Jason, Stephen, other PMC members,
>
> I can't really know if there is behind-the-scenes pmc-only discussion
> going on, but is there any chance to get 3.2.1 released this week?
>
> I need to do legal/IP paperwor
On Thu, 20 Feb 2014 12:15:57 +0100
Arnaud Héritier wrote:
+1
tested on nuiton.org, chorem.org and some codehaus.
Works fine to me.
thanks,
tony.
> My +1
> Tested on few projects and found no issue
> I just find strange the new INFO log at startup :
>
> [INFO] Using the builder
> org.apache.
My +1
Tested on few projects and found no issue
I just find strange the new INFO log at startup :
[INFO] Using the builder
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder
with a thread count of 1
Probably to put in verbose in the future ?
cheers
On Thu, Feb
My bad. I think there are only two PMC votes cast (mine and Jason's) so he
may need one more
On Thursday, 20 February 2014, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Igor,
>
> There has been no traffic on the private list.
>
> By my counting, Jason has the required number of bi
Igor,
There has been no traffic on the private list.
By my counting, Jason has the required number of binding votes, so it is up
to him to close the vote.
On Thursday, 20 February 2014, Igor Fedorenko wrote:
> Jason, Stephen, other PMC members,
>
> I can't really know if there is behind-the-sc
Jason, Stephen, other PMC members,
I can't really know if there is behind-the-scenes pmc-only discussion
going on, but is there any chance to get 3.2.1 released this week?
I need to do legal/IP paperwork for upcoming m2e 1.5 release by
this coming Friday, and I would really like to list Maven 3.
+1 (binding)
-Stephen
On 17 February 2014 01:13, Jason van Zyl wrote:
> Cool. No dire rush.
>
> On Feb 16, 2014, at 2:31 PM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > Jason, FYI I intend testing tomorrow AM (GMT). Expect my vote by noon/1pm
> > GMT
> >
> > On Sunday, 1
Cool. No dire rush.
On Feb 16, 2014, at 2:31 PM, Stephen Connolly
wrote:
> Jason, FYI I intend testing tomorrow AM (GMT). Expect my vote by noon/1pm
> GMT
>
> On Sunday, 16 February 2014, Mirko Friedenhagen
> wrote:
>
>> +1 (non-binding)
>> Regards Mirko
>> --
>> http://illegalstateexception
Jason, FYI I intend testing tomorrow AM (GMT). Expect my vote by noon/1pm
GMT
On Sunday, 16 February 2014, Mirko Friedenhagen
wrote:
> +1 (non-binding)
> Regards Mirko
> --
> http://illegalstateexception.blogspot.com/
> https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
> https
+1 (non-binding)
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Sun, Feb 16, 2014 at 10:14 PM, Baptiste Mathus wrote:
> +1 (non-binding).
>
>
> 2014-02-16 4:59 GMT+01:00 Mark
+1 (non-binding).
2014-02-16 4:59 GMT+01:00 Mark Derricutt :
> +1 here, seems to be working for all my projects.
>
> Don't seem to be getting the aether lock up either now, now I'm just
> suffering version-range hell of mixed feature branches there ( a hell of my
> own making ;p )
>
> Mark
>
>
>
+1 here, seems to be working for all my projects.
Don't seem to be getting the aether lock up either now, now I'm just
suffering version-range hell of mixed feature branches there ( a hell of
my own making ;p )
Mark
On 15 Feb 2014, at 6:58, Jason van Zyl wrote:
Specifically the zip, tarbal
Sounds like a plan.
On Feb 14, 2014, at 5:58 PM, Paul Benedict wrote:
> Okay. If that's the way to proceed, then I'd kindly recommend simply
> renaming the JIRA version (3.2.0 => 3.2.1) rather than leaving an empty
> version behind. What do you think?
>
>
> On Fri, Feb 14, 2014 at 4:54 PM, Jas
Okay. If that's the way to proceed, then I'd kindly recommend simply
renaming the JIRA version (3.2.0 => 3.2.1) rather than leaving an empty
version behind. What do you think?
On Fri, Feb 14, 2014 at 4:54 PM, Jason van Zyl wrote:
> I think they all need to be grouped under one version for the r
+1
Analyzer...
stagingUrl: https://repository.apache.org/content/repositories/maven-1006
groupId: org.apache.maven
artifactId: apache-maven
version: 3.2.1
Source ZIP url exists.
https://repository.apache.org/content/repositories/maven-1006/org/apache/maven/apache-maven/3.2.1/apache-maven-3.2.1-s
I think they all need to be grouped under one version for the release. If we
failed several times, I wouldn't always make an issue for regressions and if a
user went to look in JIRA at the 3.2.1 release and saw few issues it would
probably be confusing.
On Feb 14, 2014, at 5:44 PM, Paul Benedic
Thanks Jason. FWIW, there isn't a need to move the issues to the next patch
version when a re-spin is necessary. These tickets could have theoretically
stayed as 3.2.0 and then any new blockers that got fixed would be in the
3.2.1 queue. I think it's easier managing that way and clearer, otherwise
Hi,
+1 from me...
Checked with serveral plugin projects, with my own projects...
Checked the sha1 of the src package.
> Source release checksum(s):
> apache-maven-3.2.1-src.zip sha1: b801a145ea25c9277231030da81f36df522b7b8b
Kind regards
Karl Heinz Marbaise
> Hi,
Time to release Maven 3.2.1!
+1 all m2e tests pass
--
Regards,
Igor
On 2/14/2014, 12:58, Jason van Zyl wrote:
Hi,
Time to release Maven 3.2.1!
Here is a link to Jira with 33 issues resolved:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=20041
Staging repo:
https://repository.apache.org/conten
+1 from me. Works with ksoap2-android, android-maven-plugin and the samples.
manfred
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi,
Time to release Maven 3.2.1!
Here is a link to Jira with 33 issues resolved:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=20041
Staging repo:
https://repository.apache.org/content/repositories/maven-1006/
The distributable binaries and sources for testing can be
25 matches
Mail list logo
