You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Michael Osipov <mi...@apache.org> on 2022/04/20 16:26:22 UTC
[ANN] Maven Resolver 1.8.0 released
The Apache Maven team is pleased to announce the release of the Maven
Resolver version 1.8.0.
https://maven.apache.org/resolver/
Release Notes - Maven Resolver - Version 1.8.0
** Bug
* [MRESOLVER-241] - Resolver checksum calculation should be driven
by layout
* [MRESOLVER-242] - When no remote checksums provided by layout,
transfer inevitably fails/warns
* [MRESOLVER-250] - Usage of descriptors map in DataPool prevents
gargabe collection
** New Feature
* [MRESOLVER-236] - Make it possible to resolve .asc on a 'fail'
<checksumPolicy/> respository.
** Improvement
* [MRESOLVER-240] - Using breadth-first approach to resolve Maven
dependencies
* [MRESOLVER-247] - Avoid unnecessary dependency resolution by a
Skip solution based on BFS
* [MRESOLVER-248] - Make DF and BF collector implementations coexist
** Task
* [MRESOLVER-230] - Make supported checksum algorithms extensible
* [MRESOLVER-231] - Extend "smart checksum" feature
* [MRESOLVER-234] - Introduce "provided" checksums feature
* [MRESOLVER-237] - Make all checksum mismatches handled same
* [MRESOLVER-239] - Update and sanitize dependencies
* [MRESOLVER-244] - Deprecate FileTransformer API
* [MRESOLVER-245] - Isolate Hazelcast tests
** Dependency upgrade
* [MRESOLVER-249] - Update Hazelcast to 5.1.1 in
named-locks-hazelcast module
Enjoy,
-The Apache Maven team
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Resolver 1.8.0 released
Posted by Tamás Cservenák <ta...@cservenak.net>.
Howdy,
To use it with existing releases, you'd need to swap out the core maven
dependencies, as the plugin cannot "replace" these.
Simplest is to rebuild, see here
https://maven.apache.org/resolver/maven-3.8.x.html
Thanks
T
On Wed, Apr 20, 2022 at 11:54 PM Mark Derricutt <ma...@talios.com> wrote:
> What version of maven can this be used under? I call this from one of my
> plugins and when updating to 1.8.0 I get:
>
> Caused by: java.lang.NoSuchMethodError: 'java.util.List
>
> org.eclipse.aether.spi.connector.layout.RepositoryLayout.getChecksumAlgorithmFactories()'
> at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get
> (BasicRepositoryConnector.java:230)
> at
> org.eclipse.aether.internal.impl.DefaultMetadataResolver$ResolveTask.run
> (DefaultMetadataResolver.java:586)
> at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run
> (RunnableErrorForwarder.java:75)
> at org.eclipse.aether.internal.impl.DefaultMetadataResolver$1.execute
> (DefaultMetadataResolver.java:510)
> at org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolve
> (DefaultMetadataResolver.java:353)
> at
> org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolveMetadata
> (DefaultMetadataResolver.java:181)
> at
> org.apache.maven.repository.internal.DefaultVersionRangeResolver.getVersions
> (DefaultVersionRangeResolver.java:198)
> at
> org.apache.maven.repository.internal.DefaultVersionRangeResolver.resolveVersionRange
> (DefaultVersionRangeResolver.java:148)
> at
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveVersionRange
> (DefaultRepositorySystem.java:247)
>
>
> when running under Maven 3.8.5 - I only updated the following deps:
>
> resolved org.apache.maven.resolver:maven-resolver-api:1.8.0;
> resolved org.apache.maven.resolver:maven-resolver-connector-basic:1.8.0;
> resolved org.apache.maven.resolver:maven-resolver-impl:1.8.0;
> resolved org.apache.maven.resolver:maven-resolver-spi:1.8.0;
> resolved org.apache.maven.resolver:maven-resolver-transport-file:1.8.0;
> resolved org.apache.maven.resolver:maven-resolver-transport-http:1.8.0;
> resolved org.apache.maven.resolver:maven-resolver-util:1.8.0;
>
>
> So maybe there’s something else I need to update?
>
> --
> "Great artists are extremely selfish and arrogant things" — Steven Wilson,
> Porcupine Tree
>
>
> On 21/04/2022 at 4:26:22 AM, Michael Osipov <mi...@apache.org> wrote:
>
> > The Apache Maven team is pleased to announce the release of the Maven
> > Resolver version 1.8.0.
> >
> > https://maven.apache.org/resolver/
> >
> > Release Notes - Maven Resolver - Version 1.8.0
> >
> > ** Bug
> > * [MRESOLVER-241] - Resolver checksum calculation should be driven
> > by layout
> > * [MRESOLVER-242] - When no remote checksums provided by layout,
> > transfer inevitably fails/warns
> > * [MRESOLVER-250] - Usage of descriptors map in DataPool prevents
> > gargabe collection
> >
> > ** New Feature
> > * [MRESOLVER-236] - Make it possible to resolve .asc on a 'fail'
> > <checksumPolicy/> respository.
> >
> > ** Improvement
> > * [MRESOLVER-240] - Using breadth-first approach to resolve Maven
> > dependencies
> > * [MRESOLVER-247] - Avoid unnecessary dependency resolution by a
> > Skip solution based on BFS
> > * [MRESOLVER-248] - Make DF and BF collector implementations coexist
> >
> > ** Task
> > * [MRESOLVER-230] - Make supported checksum algorithms extensible
> > * [MRESOLVER-231] - Extend "smart checksum" feature
> > * [MRESOLVER-234] - Introduce "provided" checksums feature
> > * [MRESOLVER-237] - Make all checksum mismatches handled same
> > * [MRESOLVER-239] - Update and sanitize dependencies
> > * [MRESOLVER-244] - Deprecate FileTransformer API
> > * [MRESOLVER-245] - Isolate Hazelcast tests
> >
> > ** Dependency upgrade
> > * [MRESOLVER-249] - Update Hazelcast to 5.1.1 in
> > named-locks-hazelcast module
> >
> >
> > Enjoy,
> >
> > -The Apache Maven team
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
Re: [ANN] Maven Resolver 1.8.0 released
Posted by Mark Derricutt <ma...@talios.com>.
What version of maven can this be used under? I call this from one of my
plugins and when updating to 1.8.0 I get:
Caused by: java.lang.NoSuchMethodError: 'java.util.List
org.eclipse.aether.spi.connector.layout.RepositoryLayout.getChecksumAlgorithmFactories()'
at org.eclipse.aether.connector.basic.BasicRepositoryConnector.get
(BasicRepositoryConnector.java:230)
at org.eclipse.aether.internal.impl.DefaultMetadataResolver$ResolveTask.run
(DefaultMetadataResolver.java:586)
at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run
(RunnableErrorForwarder.java:75)
at org.eclipse.aether.internal.impl.DefaultMetadataResolver$1.execute
(DefaultMetadataResolver.java:510)
at org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolve
(DefaultMetadataResolver.java:353)
at org.eclipse.aether.internal.impl.DefaultMetadataResolver.resolveMetadata
(DefaultMetadataResolver.java:181)
at org.apache.maven.repository.internal.DefaultVersionRangeResolver.getVersions
(DefaultVersionRangeResolver.java:198)
at org.apache.maven.repository.internal.DefaultVersionRangeResolver.resolveVersionRange
(DefaultVersionRangeResolver.java:148)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveVersionRange
(DefaultRepositorySystem.java:247)
when running under Maven 3.8.5 - I only updated the following deps:
resolved org.apache.maven.resolver:maven-resolver-api:1.8.0;
resolved org.apache.maven.resolver:maven-resolver-connector-basic:1.8.0;
resolved org.apache.maven.resolver:maven-resolver-impl:1.8.0;
resolved org.apache.maven.resolver:maven-resolver-spi:1.8.0;
resolved org.apache.maven.resolver:maven-resolver-transport-file:1.8.0;
resolved org.apache.maven.resolver:maven-resolver-transport-http:1.8.0;
resolved org.apache.maven.resolver:maven-resolver-util:1.8.0;
So maybe there’s something else I need to update?
--
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree
On 21/04/2022 at 4:26:22 AM, Michael Osipov <mi...@apache.org> wrote:
> The Apache Maven team is pleased to announce the release of the Maven
> Resolver version 1.8.0.
>
> https://maven.apache.org/resolver/
>
> Release Notes - Maven Resolver - Version 1.8.0
>
> ** Bug
> * [MRESOLVER-241] - Resolver checksum calculation should be driven
> by layout
> * [MRESOLVER-242] - When no remote checksums provided by layout,
> transfer inevitably fails/warns
> * [MRESOLVER-250] - Usage of descriptors map in DataPool prevents
> gargabe collection
>
> ** New Feature
> * [MRESOLVER-236] - Make it possible to resolve .asc on a 'fail'
> <checksumPolicy/> respository.
>
> ** Improvement
> * [MRESOLVER-240] - Using breadth-first approach to resolve Maven
> dependencies
> * [MRESOLVER-247] - Avoid unnecessary dependency resolution by a
> Skip solution based on BFS
> * [MRESOLVER-248] - Make DF and BF collector implementations coexist
>
> ** Task
> * [MRESOLVER-230] - Make supported checksum algorithms extensible
> * [MRESOLVER-231] - Extend "smart checksum" feature
> * [MRESOLVER-234] - Introduce "provided" checksums feature
> * [MRESOLVER-237] - Make all checksum mismatches handled same
> * [MRESOLVER-239] - Update and sanitize dependencies
> * [MRESOLVER-244] - Deprecate FileTransformer API
> * [MRESOLVER-245] - Isolate Hazelcast tests
>
> ** Dependency upgrade
> * [MRESOLVER-249] - Update Hazelcast to 5.1.1 in
> named-locks-hazelcast module
>
>
> Enjoy,
>
> -The Apache Maven team
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>