[jira] [Created] (MENFORCER-393) Upgrading to 3.0.0 causes `Could not build dependency tree`
johnny willer gasperi goncalves created MENFORCER-393: - Summary: Upgrading to 3.0.0 causes `Could not build dependency tree` 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 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`
[ https://issues.apache.org/jira/browse/MENFORCER-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411772#comment-17411772 ] johnny willer gasperi goncalves commented on MENFORCER-393: --- Hi Sylwester, thank you very much to comment on this. I'm not sure what you mean by setup, since I don't even have any wagon plugin/extension on my effective POM. Which place could I look for the wagon config? > Upgrading to 3.0.0 causes `Could not build dependency tree` > --- > > 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] [Comment Edited] (MENFORCER-393) Upgrading to 3.0.0 causes `Could not build dependency tree`
[ https://issues.apache.org/jira/browse/MENFORCER-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411772#comment-17411772 ] johnny willer gasperi goncalves edited comment on MENFORCER-393 at 9/8/21, 8:45 AM: Hi Sylwester, thank you very much to comment on this. We are not using wagon, but I see Maven Enforcer uses it, i didn't see on the usage page a need for configure wagon, is that necessary? can you give more info on how to setup that? When using Maven enforcer v1.4.1 this was not needed was (Author: johnnywiller): Hi Sylwester, thank you very much to comment on this. I'm not sure what you mean by setup, since I don't even have any wagon plugin/extension on my effective POM. Which place could I look for the wagon config? > Upgrading to 3.0.0 causes `Could not build dependency tree` > --- > > 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&focusedCommentId=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)