The release contains a number of bug fixes.
Again we received contributions from the community in form of bug reports,
bug fixes, features and improvements.
Thank you and keep them coming!
Summarizing new main features and bug fixing, we have introduced
+ new parser of test patterns, let's call
+1
On 16 October 2015 at 20:37, Karl Heinz Marbaise wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12333008
>
> There are still a couple of issues left in JIRA:
>
>
Hi,
The vote has passed with the following result:
+1 (binding): Karl Heinz Marbaise, Benson Margulies, Hervé Boutemy,
Kristian Rosenvold
I will promote the artifacts to the central repo.
PMC members, please promote the source release ZIP file and add this
release the board report.
Cheers
Hi,
The vote has passed with the following result:
+1 (binding): Karl Heinz Marbaise, Benson Margulies, Daniel Kulp, Hervé
Boutemy
I will promote the artifacts to the central repo.
PMC members, please promote the source release ZIP file and add this
release the board report.
I'm on the case for the checkins. Or ducks.
On Sun, Oct 18, 2015 at 3:45 PM, Michael Osipov wrote:
> Hi,
>
> The vote has passed with the following result:
>
> +1 (binding): Karl Heinz Marbaise, Benson Margulies, Daniel Kulp, Hervé
> Boutemy
>
>
> I will promote the
The Apache Maven team is pleased to announce the release of the Maven
Checkstyle Plugin, version 2.17.
https://maven.apache.org/plugins/maven-checkstyle-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
>maven-checkstyle-plugin
2.17
yes, people doing Eclipse plugins can benefit from such ASF key (instead of the
personal key used with gpg on "classical" jars)
then: Windows executables, Eclipse plugins
this does not give a lot of use cases of this signing tools for projects using
Maven at ASF...
Regards,
Hervé
Le dimanche
Hi Tibor,
Taken from last dist-tool plugin failure/warn about inconsistencies:
[ERROR] maven-plugins: found 27 instead of 28 in http://maven.apache.org/pom/
[ERROR] maven-release-plugin: found 2.5.2 instead of 2.5.3 in
http://maven.apache.org/plugins/
I updated content: if it fails next time, it
I have updated plugins index page in CMS with latest surefire 2.19.
I see older one like dependency-plugin, however my working copy in CMS was
Updated to the latest version. I should not have discarded any previous
changes.
The dist-tool fails in Jenkins since 14th Oct.
Can we check it together
Currently we use std/out/in streams with shared memory that master process
communicates over forked jvms in Surefire project.
We in some Jira issues talked about it and it seems we came to a decision
that we may use another non-socket communication, this means File I/O.
Can we now create a s/w
+1
Regards,
Hervé
Le mardi 6 octobre 2015 04:39:33 Tibor Digana a écrit :
> Hi,
>
> We solved 50 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927
> rsion=12331679
>
> There are still a couple of issues left in JIRA:
>
I had in mind to do some backport for Maven 3.0.x, since upgrading is not
always possible because fo Aether transition to Eclipse.
I prepared a "issues to be reviewed for 3.0.6" version in Jira for this [1]
(my main driver being MNG-5477
"malformed POM" warning issued when no version in
+1
Regards,
Hervé
Le jeudi 15 octobre 2015 20:59:43 Michael Osipov a écrit :
> Hi,
>
> We solved 7 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317223
> rsion=12333072
>
> There are still a couple of issues left in JIRA:
>
+1
(I don't know how I checked this release with its checksum but voted on the
wrong thread... but for sure, I'm voting on the second take only :) )
Regards,
Hervé
Le jeudi 15 octobre 2015 03:48:00 Tibor Digana a écrit :
> Hi,
>
> We solved 57 issues:
>
Hi,
Perhaps the "code signing" feature for jars should be explained, since we
already have maven-gpg-plugin [1] to sign code, that is used for years with
great success.
>From what I read on ASF signing, it adds a feature for Windows executables,
that is checked by the OS at runtime and
GitHub user DylanLWScott opened a pull request:
https://github.com/apache/maven-plugins/pull/64
Updated to add dash for no-fork
Not sure if this is the right place to make the change. Noticed on
https://maven.apache.org/plugins/maven-javadoc-plugin/index.html the no-fork
was
Github user asfgit closed the pull request at:
https://github.com/apache/maven-plugins/pull/64
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Eclipse checks that sort of signature on jar files, as I recall.
On Sun, Oct 18, 2015 at 2:14 AM, Hervé BOUTEMY wrote:
> Hi,
>
> Perhaps the "code signing" feature for jars should be explained, since we
> already have maven-gpg-plugin [1] to sign code, that is used for
+1
2015-10-18 10:48 GMT+02:00 Hervé BOUTEMY :
> +1
> (I don't know how I checked this release with its checksum but voted on the
> wrong thread... but for sure, I'm voting on the second take only :) )
>
> Regards,
>
> Hervé
>
> Le jeudi 15 octobre 2015 03:48:00 Tibor Digana
Am 2015-10-16 um 15:01 schrieb Benson Margulies:
Maven-plugins 28 is released, of course; what's up? It worked for me,
but not for one of my co-workers.
Benson,
where you actually able to resolve your problem? From my point of view
this should not hinder the plugin release.
Michael
I never suggested that it should hinder the release. I was able to
test it myself, it's my co-worker who couldn't join in. You do have a
+1 from me, I look forward to the announcement.
On Sun, Oct 18, 2015 at 8:18 AM, Michael Osipov wrote:
> Am 2015-10-16 um 15:01 schrieb
Hi,
here is my +1
Kind regards
Karl Heinz Marbaise
On 10/16/15 11:37 AM, Karl Heinz Marbaise wrote:
Hi,
We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12333008
There are still a couple of issues left in JIRA:
Hi folks,
I am about to fix some bugs in the plugin but all ITs fail with the very
same message:
[INFO] Error stacktraces are turned on.
[DEBUG] Reading global settings from
E:\Programme\apache-maven-3.3.3\bin\..\conf\settings.xml
[DEBUG] Reading user settings from
23 matches
Mail list logo