Hi,
We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12342803
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MRESOLVER/issues?filter=allopenissues
Staging repo:
Speaking of making the plugins Java 11 ready maybe we should update
the Plexus Parent POM as some of the plugins are not compatible with
Java 11 (Enforcer plugin in particular) and that blocks the CI builds
of some Plexus projects. What do you think?
Regards,
Plamen Totev
On Wed, Oct 3, 2018 at
Most of the issues look like maintenance, very small chance of regression
so to me it is safe to add this to Maven 3.6.0. We don't have any feedback
yet on this Wagon release.
Just be aware that if we hit regression we must try to fix it ASAP.
Robert
On Sat, 06 Oct 2018 09:58:56 +0200,
FYI, just ran the following goal:
mvn compile org.sonatype.ossindex.maven:ossindex-maven-plugin:audit
Result on all modules is a CVSS-score threshold: 0.0
In contrast: IIRC the owasp dependency plugin gave several false positives.
We should consider to add this to the maven-parent to get
Am 2018-09-13 um 22:20 schrieb Karl Heinz Marbaise:
Hi,
based on the issues have been solved..
from my point of view waiting at the moment for the following issues:
* MNG-6311
* MNG-6391
Afterwards I would like to cut a release of Maven Core...
This results into the question:
Should we
Am 2018-10-05 um 08:40 schrieb Karl Heinz Marbaise:
Hi,
On 02/10/18 21:56, Michael Osipov wrote:
Am 2018-10-02 um 18:11 schrieb Karl Heinz Marbaise:
> Hi,
>
> Now MNG-6164
>
> will come into play?
>
> What do you think ?
Hopefully, let's push it.
From my point of view of course go
