[ 
https://issues.apache.org/jira/browse/MENFORCER-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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}
    <dependency>
      <groupId>org.apache.logging.log4j</groupId>
      <artifactId>log4j-core</artifactId>
      <version>${log4j2.version}</version>
      <scope>test</scope>
      <exclusions>
          <!-- depends on org.osgi.core 4.3.1 -->
          <exclusion>
              <groupId>org.osgi</groupId>
              <artifactId>org.osgi.core</artifactId>
          </exclusion>
      </exclusions>
    </dependency>
{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)

Reply via email to