[
http://jira.codehaus.org/browse/MNG-4110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-4110.
-----------------------------
Assignee: Brett Porter
Resolution: Won't Fix
this is still correct. Consider if you had pmd:check bound to the lifecycle,
then ran "mvn install". This would run in the parent, requiring the child to
have run first, but the child obvious requires the parent to run first.
You need to separate the parent into 2 - one that modules that need to use PMD
can inherit from, and the common stuff that that parent and the build-tools
module can inherit from.
> cyclic reference with 2.1.0 that doesn't matter with 2.0.10
> -----------------------------------------------------------
>
> Key: MNG-4110
> URL: http://jira.codehaus.org/browse/MNG-4110
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.1.0
> Environment: Linux
> Reporter: Stephan Kleine
> Assignee: Brett Porter
> Attachments: maven-bugreport.tar.bz2
>
>
> The situation is that we have a parent pom.xml (projectA in the attachment)
> which is the parent of every other project. One of the other projects is the
> one where we define global configuration files for e.g. Checkstyle & PMD
> checks (projectB in the attachment).
> The cycle exists because projectA refers to projectB in the Checkstyle & PMD
> plugin configuration and projectA is the parent of projectB.
> IMHO this shouldn't matter (as it as with Maven 2.0.10 and earlier) because
> projectA is only packaged as a pom and therefore the cycle isn't relevant.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
