Thanks for the info.
Maven updates for those not using maven wrapper take considerably longer to
work around. So that was my main concern as I couldn't really see the value on
this one. There are so many platforms that must be updated and outside of
maven wrapper, maven is not treated as a de
Howdy,
I'd like to pitch some discussion regarding Resolver near and longer term
future.
If you look at the JIRA version "planned for" 1.10.0, there are quite some
(even partially done) code changes that are not trivial. Moreover, we want
to drop some deprecated baggage as well:
https://issues.ap
Hi all,
Is it worth including more detailed information in the release notes to
short circuit questions or concerns like this one?
I can't recall the last time I hear someone complaining about releasing too
soon ;-) AFAIAC, if any bug fix is made available in a release, that's a
good thing. I'm a
Howdy,
We solved 7 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628&version=12353358
There are still some issues in JIRA:
https://issues.apache.org/jira/projects/MRESOLVER/issues
Staging repository:
https://repository.apache.org/content/repositories/maven-1978/
Howdy,
mostly bug fixes in Resolver (that is shipped embedded within Maven), and
some minor fixes in Maven itself:
- resolver had 2 notable bugs, one in new BF collector (endless loop, SOEx)
that blocked VSCode Maven integration users, and a "cluster" of multiple
smaller bugs rendering provided ch
