The Maven team is pleased to announce the release of the Apache Maven GPG
Plugin, version 1.6
Signs the project artifacts with GnuPG.
http://maven.apache.org/plugins/maven-gpg-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-gpg
JIRA created, pull request with more mature fix attached (including
integration test).
https://jira.codehaus.org/browse/SUREFIRE-1136
https://github.com/apache/maven-surefire/pull/80
Regards,
NW
On Mon, Jan 19, 2015 at 8:03 AM, Karl Heinz Marbaise
wrote:
> Hi Norbert,
>
> It's great that you a
GitHub user norbertwnuk opened a pull request:
https://github.com/apache/maven-surefire/pull/80
SUREFIRE-1136 Current working directory propagation in forked mode
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/norbertwnuk/maven-
Hi Dan,
On 1/19/15 8:00 PM, Dan Tran wrote:
Hi,
The vote has passed with the following result:
+1 (binding): Karl-Heinz Marbaise, Hervé Boutemy, Jason van Zyl
I will promote the artifacts to the central repo.
PMCs please promote the source release ZIP file and add this release the
board rep
Hi,
The vote has passed with the following result:
+1 (binding): Karl-Heinz Marbaise, Hervé Boutemy, Jason van Zyl
I will promote the artifacts to the central repo.
PMCs please promote the source release ZIP file and add this release the
board report.
Thanks
-Dan
I really like this solution
Robert
Op Sun, 18 Jan 2015 22:48:37 +0100 schreef :
Author: hboutemy
Date: Sun Jan 18 21:48:36 2015
New Revision: 1652861
URL: http://svn.apache.org/r1652861
Log:
[MCHECKSTYLE-249] updated ITs to not fail when distribution created on
Unix and ITs run on Windows
Hi Tom,
first step would be to create a JIRA item where you describe your
improvements etc. and there you can add a patch which you have
created...Of course it would be good having tests for your improvements
which makes it easier for the devs to integrate your changes into the
code base...
Hi Norbert,
It's great that you asking for permission to create a jira but you don't
need to just create one and describe the situation etc. why and how it
went wrong or what can be improved and of course your patch is really
great...but it would be much easier if you could either provide a te
