I will cut the release the week after next. I’m going to work on a little
testing infrastructure this week.
> On Jul 30, 2015, at 11:41 PM, Jason van Zyl wrote:
>
> Hi,
>
> Time to release Maven 3.3.6!
>
> Here is a link to the issues resolved:
> https://issues.apache.org/jira/secure/ReleaseN
I will cancel the vote.
> On Aug 1, 2015, at 9:08 AM, Karl Heinz Marbaise wrote:
>
> Hi,
>
> +0 from me...
>
> Reference Documentation updated (http://maven.apache.org/ref/3-LATEST/)..
>
> checked with maven-invoker-plugin, maven-install-plugin, with Maven itself
> ;-)...
> and with some of
It’s not your fault, we have an appallingly bad CI setup. Humans should not
have to catch these issues. We even have tests, but seems we can’t figure out
how to run them in a meaningful way to avoid manual testing.
> On Aug 1, 2015, at 11:05 AM, Anton Tanasenko wrote:
>
> I've created yet anot
I've created yet another PR for MNG-5805:
https://github.com/apache/maven/pull/62
Sorry guys, I was certain I had run m-enforcer-p its as well with 3.3.5
candidate.
2015-08-01 16:57 GMT+03:00 Anton Tanasenko :
> Oh not again,
> The LifecyclePhase#toString() method was added by me along with
> toL
GitHub user atanasenko opened a pull request:
https://github.com/apache/maven/pull/62
MNG-5805: Fix NPE in LifecyclePhase#toString()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/atanasenko/maven master
Alternatively you can r
Oh not again,
The LifecyclePhase#toString() method was added by me along with toLegacyMap.
Looks like I didn't take care of 'mojos' field possibly being null. This
seems to be happening when an extension specifies a lifecycle phase but
doesn't assign any mojo executions to it.
2015-08-01 16:08 GM