You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Karl-Heinz Marbaise (JIRA)" <ji...@codehaus.org> on 2014/06/23 14:01:10 UTC
[jira] (MENFORCER-196) ReactorModuleConvergence Enhancement to
identify special scenarios
Karl-Heinz Marbaise created MENFORCER-196:
---------------------------------------------
Summary: ReactorModuleConvergence Enhancement to identify special scenarios
Key: MENFORCER-196
URL: https://jira.codehaus.org/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
(v6.1.6#6162)