[jira] [Closed] (MENFORCER-196) ReactorModuleConvergence Enhancement to identify special scenarios

["Robert Scholte (Jira)" <ji...@apache.org>]

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

Robert Scholte closed MENFORCER-196.
------------------------------------
      Assignee: Robert Scholte
    Resolution: Won't Fix

The suggested approach is too fragile and might lead to false negatives. 
Knowing that with Maven 4 we don't need to define versions for reactor dependencies anymore I prefer to drop this request.

> ReactorModuleConvergence Enhancement to identify special scenarios
> ------------------------------------------------------------------
>
>                 Key: MENFORCER-196
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-196
>             Project: Maven Enforcer Plugin
>          Issue Type: Improvement
>          Components: Standard Rules
>    Affects Versions: 1.4
>         Environment: all
>            Reporter: Karl Heinz Marbaise
>            Assignee: Robert Scholte
>            Priority: Minor
>
> Scenario:
> Large number of modules now changing the pom structure and of course the groupId/artifactId's as well but accidently left over a single groupId/artifactId/version reference of the old structure. 
> Result:
> current builds will run sucessfully, cause the artifact is found in the snapshot repository but it's not part of the reactor. This will fail only in case of creating the release if the SNAPSHOT repository will be deleted.
> If we found an GAV, where V is equal to the current version in the reactor we could at leat produce a WARNING for such cases (best is to suppress this warning if needed).
> More reliable we can check if this artifact contains dependencies on artifacts within the reactor. Than is definitely and wrong GAV which must be fixed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)