The Apache Maven team is pleased to announce the release of the
Maven Resolver 2.0.0-alpha-11.

https://maven.apache.org/resolver-archives/resolver-2.0.0-alpha-11/

This is the last alpha release of Resolver 2.0.0, that would allow any
downstream consumers to try it out and adapt.

Release Notes - Maven Resolver - Version 2.0.0-alpha-11

** Bug
    * [MRESOLVER-521] - File locking threads not entering critical region
were "oversleeping"
    * [MRESOLVER-547] - BF collector always copies artifacts, even when it
should not
** New Feature
    * [MRESOLVER-217] - Allow extra "sources" for Artifact decoration
    * [MRESOLVER-518] - Improvements for version selector
** Improvement
    * [MRESOLVER-519] - Drop copies of same method, re-add them to parent
(collectors)
    * [MRESOLVER-520] - Move repeated code (decorators, generators) into
Utils
    * [MRESOLVER-535] - DependencyGraphDumper should be configurable
    * [MRESOLVER-536] - Skip setting last modified time when FS does not
support it
    * [MRESOLVER-538] - In dirty tree, nodes coming from range (and parents
having ranges) should be detectable
    * [MRESOLVER-540] - TransferResource can and should tell more about
transfer
    * [MRESOLVER-542] - Reduce usage of final classes
** Task
    * [MRESOLVER-552] - Redirect site creation to enable concurrent release
of 1.x and 2.x resolver
** Dependency upgrade
    * [MRESOLVER-523] - Update GPG generator to Bouncycastle 1.78
    * [MRESOLVER-524] - Update Hazelcast to 5.3.7
    * [MRESOLVER-525] - Update test dep testcointainers-redis to 2.2.2
    * [MRESOLVER-534] - Redisson 3.28.0
    * [MRESOLVER-537] - Use slf4j 2.0.13
    * [MRESOLVER-539] - Use parent POM 42
    * [MRESOLVER-543] - (build) Bump
com.github.siom79.japicmp:japicmp-maven-plugin from 0.20.0 to 0.21.1
    * [MRESOLVER-544] - Bump org.redisson:redisson from 3.28.0 to 3.29.0
    * [MRESOLVER-545] - Bump bouncycastleVersion from 1.78 to 1.78.1
    * [MRESOLVER-546] - Bump org.codehaus.plexus:plexus-utils from 4.0.0 to
4.0.1


Have fun,
-The Apache Maven team

Reply via email to