maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Fox (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MENFORCER-14) Enforcer Plugin Messes Up Dependencies
Date Fri, 03 Aug 2007 00:23:13 GMT

    [ http://jira.codehaus.org/browse/MENFORCER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103899
] 

Brian Fox commented on MENFORCER-14:
------------------------------------

You're right, it's not a fix but a workaround. However, the enforce-once has always been broken
and executes on each project anyway. Therefore, there is no speed/performance difference between
the two.

> Enforcer Plugin Messes Up Dependencies
> --------------------------------------
>
>                 Key: MENFORCER-14
>                 URL: http://jira.codehaus.org/browse/MENFORCER-14
>             Project: Maven 2.x Enforcer Plugin
>          Issue Type: Bug
>            Reporter: James Carman
>            Assignee: Brian Fox
>         Attachments: toplevel.zip
>
>
> When using the enforcer plugin, it somehow messes up the dependencies in a reactor-based
build. The attached zip file exhibits the problem. Our project structure is a bit weird. We
have one top-level project which contains a bunch of modules. One of the modules is a pom-based
"tempalte" project which sets up all of our build settings (src/target for the compiler, turns
on the aspectj compiler, etc.). All of the other modules extend the "template" project and
they themselves have multiple sub-project.

-- 
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

        

Mime
View raw message