[
https://issues.apache.org/jira/browse/MENFORCER-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MENFORCER-196.
------------------------------------
Resolution: Auto Closed
This issue has been auto closed because it has been inactive for a long period
of time. If you think this issue still applies, retest your problem with the
most recent version of Maven and the affected component, reopen and post your
results.
> 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
> 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
(v7.6.3#76005)