You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Olivier Lamy (Jira)" <ji...@apache.org> on 2021/09/12 11:09:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Olivier Lamy updated MENFORCER-393:
-----------------------------------
Summary: Upgrading to 3.0.0 causes `Could not build dependency tree` with repositories some unknown protocol (was: Upgrading to 3.0.0 causes `Could not build dependency tree`)
> 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)