Re: [VOTE] Release Maven Help Plugin version 3.0.0

Am 2018-03-07 um 22:37 schrieb Michael Osipov: Hi, We solved 34 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317522=12330788 There are still a couple of issues left in JIRA:

Re: Plans to release 3.0.0 of the ear plugin?

I will be able to, but not likely until the 19th when I have access to more projects. Most of our use at work is pretty plain so I won't be very complicated cases. Would that work? Jim On Wed, Mar 7, 2018 at 3:29 PM Karl Heinz Marbaise wrote: > Hi Jim, > > do you have the

Re: [ANN] Apache Maven 3.5.3 Released

Hi Fred, On 09/03/18 05:02, Fred Cooke wrote: 3.5.3 as per subject and list or 3.5.2 as per opening sentence? Guessing the former. Of course 3.5.3 is the correct number ;-) Kind regards Karl Heinz Marbaise [1]: http://maven.apache.org/docs/history.html On 9 March 2018 at 01:31, Stephen

Re: [m-jlink-p] NPE for small project

Hi, On 09/03/18 01:40, Bernd Eckenfels wrote: Hello, just found that this is a known and fixed issue: https://issues.apache.org/jira/browse/MJLINK-4 Gruss Bernd Do you have a chance to test a SNAPSHOT version of the plugin? I have uploaded a version into :

Re: [ANN] Apache Maven 3.5.3 Released

3.5.3 as per subject and list or 3.5.2 as per opening sentence? Guessing the former. On 9 March 2018 at 01:31, Stephen Connolly wrote: > The Apache Maven team is pleased to announce the release of the Apache > Maven 3.5.2 > > You can download the appropriate sources etc.

Re: dist tool failed

Hi I tracked the issue: dist-tools is looking for *.md5 only, not *.sha1 in dist And the error message is not clear, since it is written for the usual failure = wrong version, since this new extension case was really not expected I'll fix shortly Regards, Hervé Le jeudi 8 mars 2018,

Re: RFC: Maven to raise a notification if downloading vulnerable content

on the "better education" journey, I started by adding OWASP Dependency Check to our list of remarkable third party projects that provide a Maven plugin http://maven.apache.org/plugins/index.html#Misc Don't hesitate to provide little patches for other documentation improvements Regards,

Re: [m-jlink-p] NPE for small project

Hello, just found that this is a known and fixed issue: https://issues.apache.org/jira/browse/MJLINK-4 Gruss Bernd -- http://bernd.eckenfels.net Von: Bernd Eckenfels Gesendet: Freitag, 9. März 2018 01:37 An: Maven Developers List Betreff: [m-jlink-p] NPE for small project Hello, when I use

[m-jlink-p] NPE for small project

Hello, when I use a simple POM like this: http://maven.apache.org/POM/4.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd;> 4.0.0

Re: dist tool failed

I removed the old dist in second SVN commit. Would it be the case? On Thu, Mar 8, 2018 at 7:31 PM, Karl Heinz Marbaise wrote: > Hi to all, > > our dist-tool[1] has failed base on the following: > > [INFO] maven-fluido-skin > [INFO] /surefire: org.apache.maven.surefire >

Re: dist tool failed

Hi Tibor, unfortunately I don't know what wrong at .. Maybe I've have to check the code the dist tool to understand what the problem is... Kind regards Karl Heinz Marbaise On 08/03/18 21:56, Tibor Digana wrote: Karl, am I doing something wrong? I also checked sha1 and version. On Thu,

Re: dist tool failed

Karl, am I doing something wrong? I also checked sha1 and version. On Thu, Mar 8, 2018 at 7:31 PM, Karl Heinz Marbaise wrote: > Hi to all, > > our dist-tool[1] has failed base on the following: > > [INFO] maven-fluido-skin > [INFO] /surefire: org.apache.maven.surefire >

dist tool failed

Hi to all, our dist-tool[1] has failed base on the following: [INFO] maven-fluido-skin [INFO] /surefire: org.apache.maven.surefire [INFO] surefire [ERROR] Different version than 2.21.0 for surefire available in http://www.apache.org/dist/maven/surefire [ERROR] >

Re: Spring cleanup JIRA

Am 2018-03-07 um 23:31 schrieb Michael Osipov: Folks, I did yet another analysis on open issues. We have currently more than 400 open issues which haven't been touched for more than three (3) years. The last two times I autoclosed them with a message. People could request a reopen, very

Re: Spring cleanup JIRA

100 for the whole Maven project? Luckily we have ~85 projects, so the damage looks manageable. However, with a total of 2000+ open issues and with the current active resources it is impossible to fix them all. So yes, close them as Auto-Close with a clear message. I sometimes look at

Re: [ANN] Apache Maven 3.5.3 Released

What is the project about? Why should I be interested in it? [rhetorical questions] The Announce emails are sent to people not on the developer or user lists. Most will have no idea what the project is about. So the e-mails should contain at least brief details of what the product does, and some

[ANN] Apache Maven 3.5.3 Released

The Apache Maven team is pleased to announce the release of the Apache Maven 3.5.2 You can download the appropriate sources etc. from the download page Contributors The Apache Maven team would like to thank the following contributors, without whom this release would not have been

[ANN] Apache Maven 3.5.3 Released

The Apache Maven team is pleased to announce the release of the Apache Maven 3.5.2 You can download the appropriate sources etc. from the download page Contributors The Apache Maven team would like to thank the following contributors, without whom this release would not have been

Re: Spring cleanup JIRA

Non binding but agreed - once an issue list gets beyond 50 it's hard to see the forest, once it's beyond 100 you can pretty much guarantee that everyone is lost. Cheers, Martijn On 8 March 2018 at 07:45, Anders Hammar wrote: > +1 for the same process as last time. > >