You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2023/12/03 19:40:00 UTC

[jira] [Updated] (MENFORCER-484) [Question/Bug?] about requireSameVersion

     [ https://issues.apache.org/jira/browse/MENFORCER-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov updated MENFORCER-484:
-------------------------------------
    Fix Version/s:     (was: waiting-for-feedback)

> [Question/Bug?] about requireSameVersion
> ----------------------------------------
>
>                 Key: MENFORCER-484
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-484
>             Project: Maven Enforcer Plugin
>          Issue Type: Bug
>          Components: requireSameVersions
>            Reporter: Eugenio Lentini
>            Priority: Major
>
> Hello,
> I am using the {{requireSameVersion}} rule but it does not print, like the dependency convergence, where issues are.
> There is just an error but via {{mvn dependency:tree -Dverbose}} I cannot see any conflict.
> Questions:
>  * How does it suppose to work this rule?
>  * Is it possible to print the tree as in dependencyConvergence?
>  * What is the difference between requireSameVersion and dependencyConvergence?
> Thanks in advance for the answers.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)