Am 2023-11-21 um 21:00 schrieb Michael Osipov:
Hi,
we solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353750
There is one issue left in JIRA:
Am 2023-11-21 um 21:12 schrieb Michael Osipov:
Hi,
IMPORTANT: This require the following staging repositories:
* Maven Reporting Impl 4.0.0-M12
we solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12353779
There are still a couple of issues left in
Am 2023-11-21 um 22:22 schrieb Michael Osipov:
Hi,
IMPORTANT: This require the following staging repositories:
* Maven Reporting Impl 4.0.0-M12
* Maven Reporting Exec 4.0.0-M12
we solved 7 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12353780
There are
Howdy,
Note1: Maven Resolver 1.x lineage is in "bugfix only" maintenance mode.
Note2: Resolver 1.9.17 release is declared "broken" by RM, release 1.9.18
undos the unwanted code change that happened in FileUtils@1.9.17 and
restores source compatibility between 2.x and 1.9.x.
We solved 2 issues:
Howdy,
since 1.9.17 release went out, we detected some possible problems with
1.9.17 and decided to quickly roll out 1.9.18 with two important changes:
- MRESOLVER-372 fix in 1.9.17 introduced some unwanted changes in FileUtils
non-Windows execution path (undo those),
- backport MRESOLVER-437,