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 i...@ifedorenko.com wrote:
Jason, Stephen, other PMC members,
I can't really know if there
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 binding
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
On Thu, 20 Feb 2014 12:15:57 +0100
Arnaud Héritier aherit...@gmail.com 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
+1
finally it's agile @apache :P
On 20 February 2014 13:30, Igor Fedorenko i...@ifedorenko.com 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
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
Register for an xircles account on Codehaus and you will have JIRA access.
Commit comes from sustained participation.
On February 20, 2014 8:33:12 AM EST, Ashish Patel ashish.pate...@gmail.com
wrote:
Hi,
What would it take for me to get JIRA access to create tickets and/or
comment?
I would
Hi,
What would it take for me to get JIRA access to create tickets and/or
comment?
I would like to add patch file to an existing ticket (
http://jira.codehaus.org/browse/MCHANGES-327). I am hoping this would help
it get completed sooner.
Commit access would be great too. Let me know if this is
Here is a link https://xircles.codehaus.org/signup/ you can find it on
https://jira.codehaus.org/secure/Dashboard.jspa in introduction section.
Wiadomość napisana przez Ashish Patel ashish.pate...@gmail.com w dniu 20 lut
2014, o godz. 14:33:
Hi,
What would it take for me to get JIRA
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.
On 21 February 2014 06:11, Benson Margulies bimargul...@gmail.com wrote:
Register for an xircles account on Codehaus and you will have JIRA access.
Commit comes from sustained participation.
You can read some more at
Stephen,
I think the recent process of releasing the core makes it clear that weekly
official releases is not a viable concept. In the course of a week, 4 of the 25
PMC members voted and we haven't had a release in 6 months. Highly unlikely
we'll get a better turnout more frequently. I don't
Hi Jason
While I'm finally starting to see the potential with a DVCS like git,
there are a couple of things that stands in the way of migrating, for
example plugins, to git:
1. Judging by our resident git gurus, it will require quite some
effort to prepare for and execute the actual migration.
Would it be a good test to first try migrating individual plugin projects
to GIT before attempting Maven Core?
On Thu, Feb 20, 2014 at 3:07 PM, Dennis Lundberg
dennisl.apa...@gmail.comwrote:
Hi Jason
While I'm finally starting to see the potential with a DVCS like git,
there are a couple of
Maven Core is in git and has been for quite some time now... or you mean
some other Mave Core?
https://git-wip-us.apache.org/repos/asf?p=maven.git
--
Regards,
Igor
On 2/20/2014, 16:12, Paul Benedict wrote:
Would it be a good test to first try migrating individual plugin projects
to GIT before
Here are my thoughts on the discussions.
If we can get a tool chain working in Jenkins that build maven-core
and runs the ITs in an automated and reliable way - that's great. The
gold star in that should be the bare minimum required to do a release.
I see it as a stamp of approval that the
On Feb 20, 2014, at 1:07 PM, Dennis Lundberg dennisl.apa...@gmail.com wrote:
Hi Jason
While I'm finally starting to see the potential with a DVCS like git,
there are a couple of things that stands in the way of migrating, for
example plugins, to git:
1. Judging by our resident git
On Thu, Feb 20, 2014 at 4:27 PM, Jason van Zyl ja...@takari.io wrote:
On Feb 20, 2014, at 1:07 PM, Dennis Lundberg dennisl.apa...@gmail.com wrote:
Hi Jason
While I'm finally starting to see the potential with a DVCS like git,
there are a couple of things that stands in the way of migrating,
I am in favor of using a stricter-than-today SEMVER-ish approach to
our releases, not just in core but in all our releases.
To me it's really easy. Just check the issue types in JIRA and let
that decide which version number will come next. If there are only
bugs fixed then it's a patch-release,
The entire SCM interface is very SVN-centric IMO. I raised a number of git
related m-rel-p issues some time ago, but have been busy moving countries
and more in the mean time. I doubt there has been progress on them, though.
One pretty much required a core change to Maven (perhaps something for
Well I guess we disagree as to how to get towards getting fixes to users
faster. My personal belief is that it is better to set out the goal and
find'n'fix the problems on the way to that goal rather than say there are
too many problems for now that we can't get to that goal.
I think weekly
On Thu, Feb 20, 2014 at 10:27 PM, Jason van Zyl ja...@takari.io wrote:
On Feb 20, 2014, at 1:07 PM, Dennis Lundberg dennisl.apa...@gmail.com wrote:
Hi Jason
While I'm finally starting to see the potential with a DVCS like git,
there are a couple of things that stands in the way of
On 20 February 2014 21:22, Dennis Lundberg dennisl.apa...@gmail.com wrote:
Here are my thoughts on the discussions.
If we can get a tool chain working in Jenkins that build maven-core
and runs the ITs in an automated and reliable way - that's great. The
gold star in that should be the bare
On 20 February 2014 21:30, Dennis Lundberg dennisl.apa...@gmail.com wrote:
I am in favor of using a stricter-than-today SEMVER-ish approach to
our releases, not just in core but in all our releases.
To me it's really easy. Just check the issue types in JIRA and let
that decide which version
On 21 Feb 2014, at 10:27, Jason van Zyl wrote:
I only release core and that works fine which begs the question: do we
want to normalize our repository structure to simplify the tooling
requirements. What exactly doesn't work? Trying to release a single
thing out of a repository containing
That is easily worked around tho by adding a dependency setting for
the newer -scm- modules.
mark
On 21 Feb 2014, at 10:29, Benson Margulies wrote:
The M-R-P has a giant bug such that the current version of it and the
current version of git do not work together. I think the bug is
Yep. I release projects every day with git and m-r-p. The only issues I
know of are if you are wanting to release a portion of the repository or a
reactor that does not start at the root of the repository... but I don't do
that and I think it is a stupid thing to do anyway, so not a problem for me
+extension
+groupIdorg.apache.maven.wagon/groupId
+artifactIdwagon-ssh-external/artifactId
+version${extension.version.wagon}/version
+/extension
It was SSH settings that were not being respected. Things like ports and
ssh
28 matches
Mail list logo
