+1
Regards,
Hervé
Le mercredi 7 mars 2018, 22:37:46 CET Michael Osipov a écrit :
> Hi,
>
> We solved 34 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317522&ve
> rsion=12330788
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/
Hi,
We solved 41 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317422&version=12330696
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MEAR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DES
+1
Le 07/03/2018 à 22:37, Michael Osipov a écrit :
Hi,
We solved 34 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317522&version=12330788
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPH%20AND%20res
Personally, I think vulnerable packages could be retained locally and was
subscribable. Dealing with it during a build would be a local operation.
Here's a repo of all Maven Meta data (I wrote some stuff in Python and
Herve redid it in Java) -> https://github.com/hboutemy/mcmm-yaml/
While vulnera
2018-03-09 9:55 GMT+01:00 Tibor Digana :
> Hi Enrico, Karl, Herve,
>
> We reported the issues [1] found during the Vote. They are fixed in
> branches [2] and CI builds [3].
> We can make a code review.
> Additionally, we fixed SUREFIRE-1490 which was in progress but we did not
> have spare time to
Hi Enrico, Karl, Herve,
We reported the issues [1] found during the Vote. They are fixed in
branches [2] and CI builds [3].
We can make a code review.
Additionally, we fixed SUREFIRE-1490 which was in progress but we did not
have spare time to include it in the Release 2.21.0. Now it is fixed in [
