You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Matt Raible (Jira)" <ji...@apache.org> on 2022/02/16 19:39:00 UTC

[jira] [Created] (MENFORCER-413) Upgrading from 3.0.0-M3 to 3.0.0 causes strange errors about Spring Roo

Matt Raible created MENFORCER-413:
-------------------------------------

             Summary: Upgrading from 3.0.0-M3 to 3.0.0 causes strange errors about Spring Roo
                 Key: MENFORCER-413
                 URL: https://issues.apache.org/jira/browse/MENFORCER-413
             Project: Maven Enforcer Plugin
          Issue Type: Bug
          Components: Plugin
    Affects Versions: 3.0.0
            Reporter: Matt Raible


In a fresh JHipster project, I get a strange error from the Maven enforcer plugin about Spring Roo dependencies.
[INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-dependencyConvergence) @ lapp-li ---
[WARNING] The POM for org.apache.logging.log4j:log4j-api-java9:zip:2.14.1 is missing, no dependency information available
Downloading from spring-libs-snapshot: https://repo.spring.io/libs-snapshot/org/springframework/roo/org.springframework.roo.annotations/1.2.3.RELEASE/org.springframework.roo.annotations-1.2.3.RELEASE.pom
Downloading from spring-libs-release: https://repo.spring.io/libs-release/org/springframework/roo/org.springframework.roo.annotations/1.2.3.RELEASE/org.springframework.roo.annotations-1.2.3.RELEASE.pom
 
If I run {{{}mvn dependency:tree | grep roo{}}}, there are no results. 
 
According to the issue below, reverting to -M3 solves the problem.
 
https://github.com/jhipster/generator-jhipster/issues/16318



--
This message was sent by Atlassian Jira
(v8.20.1#820001)