[
https://issues.apache.org/jira/browse/MENFORCER-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17511563#comment-17511563
]
Duo Zhang commented on MENFORCER-413:
-------------------------------------
OK, the problem is that, spring-data-commons depends on querydsl-apt, and
querydsl-apt depends on org.springframework.roo.annotations, and the 1.2.x
version for org.springframework.roo.annotations is only available on
repo.spring.io, which is not public.
The reason why we can not see it in the mvn dependency:tree output is because
org.springframework.roo.annotations is declared with scope provided.
So I think the problem here for maven enforcer plugin is that it is too strict.
I think we can just ignore the optional and provided dependencies while
checking, or at least provide an option to let users ignore them.
Thanks.
> 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
> Priority: Major
> Fix For: wontfix-candidate
>
>
> 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)