You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Marcos Passos (Jira)" <ji...@apache.org> on 2021/12/17 13:40:00 UTC
[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=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)