You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Falko Modler (Jira)" <ji...@apache.org> on 2022/06/29 22:37:00 UTC
[jira] [Comment Edited] (MENFORCER-393) Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories some unknown protocol
[ https://issues.apache.org/jira/browse/MENFORCER-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17560671#comment-17560671 ]
Falko Modler edited comment on MENFORCER-393 at 6/29/22 10:36 PM:
------------------------------------------------------------------
Same here with enforcer 3.1.0 and Maven 3.8.6:
{noformat}
[ERROR] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
Could not build dependency tree Could not collect dependencies: io.quarkus:quarkus-extension-processor:jar:999-SNAPSHOT
{noformat}
{{-X}} reveals:
{noformat}
...
Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact rubygems:rubygems-update:pom:3.2.29 from/to mavengems (mavengem:https://rubygems.org): Cannot access mavengem:https://rubygems.org with type default using the available connector factories: BasicRepositoryConnectorFactory
...
Caused by: org.eclipse.aether.transfer.NoTransporterException: Unsupported transport protocol mavengem:https
...
Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException
role: org.apache.maven.wagon.Wagon
roleHint: mavengem
Caused by: java.util.NoSuchElementException
at org.eclipse.sisu.plexus.RealmFilteredBeans$FilteredItr.next (RealmFilteredBeans.java:118)
at org.eclipse.sisu.plexus.RealmFilteredBeans$FilteredItr.next (RealmFilteredBeans.java:1)
at org.eclipse.sisu.plexus.DefaultPlexusBeans$Itr.next (DefaultPlexusBeans.java:76)
at org.eclipse.sisu.plexus.DefaultPlexusBeans$Itr.next (DefaultPlexusBeans.java:1)
at org.codehaus.plexus.DefaultPlexusContainer.lookup (DefaultPlexusContainer.java:263)
at org.codehaus.plexus.DefaultPlexusContainer.lookup (DefaultPlexusContainer.java:255)
at org.eclipse.aether.internal.transport.wagon.PlexusWagonProvider.lookup (PlexusWagonProvider.java:56)
...
{noformat}
Ruby comes in via: https://github.com/quarkusio/quarkus/blob/main/core/processor/pom.xml#L42-L46
was (Author: famod):
Same here with enforcer 3.1.0 and Maven 3.8.6:
```
[ERROR] Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with message:
Could not build dependency tree Could not collect dependencies: io.quarkus:quarkus-extension-processor:jar:999-SNAPSHOT
```
{{-X}} reveals:
{noformat}
...
Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact rubygems:rubygems-update:pom:3.2.29 from/to mavengems (mavengem:https://rubygems.org): Cannot access mavengem:https://rubygems.org with type default using the available connector factories: BasicRepositoryConnectorFactory
...
Caused by: org.eclipse.aether.transfer.NoTransporterException: Unsupported transport protocol mavengem:https
...
Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: java.util.NoSuchElementException
role: org.apache.maven.wagon.Wagon
roleHint: mavengem
Caused by: java.util.NoSuchElementException
at org.eclipse.sisu.plexus.RealmFilteredBeans$FilteredItr.next (RealmFilteredBeans.java:118)
at org.eclipse.sisu.plexus.RealmFilteredBeans$FilteredItr.next (RealmFilteredBeans.java:1)
at org.eclipse.sisu.plexus.DefaultPlexusBeans$Itr.next (DefaultPlexusBeans.java:76)
at org.eclipse.sisu.plexus.DefaultPlexusBeans$Itr.next (DefaultPlexusBeans.java:1)
at org.codehaus.plexus.DefaultPlexusContainer.lookup (DefaultPlexusContainer.java:263)
at org.codehaus.plexus.DefaultPlexusContainer.lookup (DefaultPlexusContainer.java:255)
at org.eclipse.aether.internal.transport.wagon.PlexusWagonProvider.lookup (PlexusWagonProvider.java:56)
...
{noformat}
Ruby comes in via: https://github.com/quarkusio/quarkus/blob/main/core/processor/pom.xml#L42-L46
> Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories some unknown protocol
> ---------------------------------------------------------------------------------------------------
>
> Key: MENFORCER-393
> URL: https://issues.apache.org/jira/browse/MENFORCER-393
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
> Affects Versions: 3.0.0
> Reporter: johnny willer gasperi goncalves
> Priority: Major
> Attachments: enforcer_output
>
>
> After upgrading to 3.0.0, it's not possible to validate the POM anymore, an error like
> {code:java}
> Could not build dependency tree Could not collect dependencies: {jarname}{code}
> happens.
>
> I'm attaching the `mvn validate -X` dump (i have omitted some jars from the output)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)