[jira] [Commented] (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=17725132#comment-17725132
]
ASF GitHub Bot commented on MENFORCER-393:
--
slawekjaranowski merged PR #271:
URL: https://github.com/apache/maven-enforcer/pull/271
> 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: dependencyConvergence, Plugin
>Affects Versions: 3.0.0
>Reporter: johnny willer gasperi goncalves
>Assignee: Slawomir Jaranowski
>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)
[jira] [Commented] (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=17724638#comment-17724638
]
Tilman Hausherr commented on MENFORCER-393:
---
The problem I mentioned in January 2022 no longer happens with 3.3.0.
> 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: dependencyConvergence, Plugin
>Affects Versions: 3.0.0
>Reporter: johnny willer gasperi goncalves
>Assignee: Slawomir Jaranowski
>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)
[jira] [Commented] (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=17724635#comment-17724635
]
Slawomir Jaranowski commented on MENFORCER-393:
---
I added {{org.jruby:jruby-stdlib}} to IT - and looks like test pass.
Please retest with 3.3.0 version
> 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: dependencyConvergence, 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)
[jira] [Commented] (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=17724634#comment-17724634
]
ASF GitHub Bot commented on MENFORCER-393:
--
slawekjaranowski opened a new pull request, #271:
URL: https://github.com/apache/maven-enforcer/pull/271
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MENFORCER) filed
for the change (usually before you start working on it). Trivial
changes like typos do not
require a JIRA issue. Your pull request should address just this
issue, without
pulling in other changes.
- [x] Each commit in the pull request should have a meaningful subject line
and body.
- [x] Format the pull request title like `[MENFORCER-XXX] - Fixes bug in
ApproximateQuantiles`,
where you replace `MENFORCER-XXX` with the appropriate JIRA issue.
Best practice
is to use the JIRA issue title in the pull request title and in the
first line of the
commit message.
- [ ] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [x] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will
be performed on your pull request automatically.
- [x] You have run the integration tests successfully (`mvn -Prun-its clean
verify`).
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [x] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [x] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
> 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: dependencyConvergence, 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)
[jira] [Commented] (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=17560671#comment-17560671
]
Falko Modler commented on MENFORCER-393:
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)
[jira] [Commented] (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=17554206#comment-17554206
]
Tilman Hausherr commented on MENFORCER-393:
---
Still happens with 3.1.0.
> 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.7#820007)
[jira] [Commented] (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=17471279#comment-17471279
]
Tilman Hausherr commented on MENFORCER-393:
---
Maybe related: before the above comment, I had to change two entries in another
subproject due to convergence problems, like this because osgi 6 was used
elsewhere, and log4j has a weak dependency on an earlier version of osgi:
{code}
org.apache.logging.log4j
log4j-core
${log4j2.version}
test
org.osgi
org.osgi.core
{code}
> 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.1#820001)
[jira] [Commented] (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=17471170#comment-17471170
]
Tilman Hausherr commented on MENFORCER-393:
---
Same problem in the Apache Tika project. I was trying to change version from
3.0.0-M3 to 3.0.0 and one of the subprojects fails.
Old output
{noformat}
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-java-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-output-timestamp-property)
@ tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0-M3:enforce (ban-bad-log4j-versions) @
tika-parser-scientific-module ---
{noformat}
New output
{noformat}
--- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-output-timestamp-property) @
tika-parser-scientific-module ---
--- maven-enforcer-plugin:3.0.0:enforce (enforce-maven) @
tika-parser-scientific-module ---
Rule 0: org.apache.maven.plugins.enforcer.DependencyConvergence failed with
message:
Could not build dependency tree Could not collect dependencies:
org.apache.tika:tika-parser-scientific-module:jar:2.2.2-SNAPSHOT ()
{noformat}
> 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.1#820001)
[jira] [Commented] (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=17461442#comment-17461442
]
Marcos Passos commented on MENFORCER-393:
-
Exactly the same issue here.
> 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.1#820001)
[jira] [Commented] (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=17425464#comment-17425464
]
Quentin Caillard commented on MENFORCER-393:
I have this message when upgrading to 3.0.0 from 3.0.0-M3
[WARNING] Rule 5: org.apache.maven.plugins.enforcer.RequireUpperBoundDeps
failed with message:
Could not build dependency tree Could not collect dependencies:
com.mac:mac-bc360-custom:jar:9.3.2-SNAPSHOT ()
> 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.3.4#803005)
[jira] [Commented] (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=17413986#comment-17413986
]
johnny willer gasperi goncalves commented on MENFORCER-393:
---
Hi [~olamy], sorry I don't have any reproducer, the library in case is private
one. I'll do some tests, If I find one i share here. Thanks for looking at it
> 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.3.4#803005)
