You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "James Carman (JIRA)" <ji...@codehaus.org> on 2007/08/01 20:17:13 UTC
[jira] Created: (MENFORCER-14) Enforcer Plugin Messes Up
Dependencies
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
[jira] Commented: (MENFORCER-14) Enforcer Plugin Messes Up
Dependencies
Posted by "James Carman (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103863 ]
James Carman commented on MENFORCER-14:
---------------------------------------
I would disagree that changing "enforce-once" to "enforce" is a "fix". That is at best a work-around. As Andrew Perepelytsya said on the related duplicate issue, this will slow down the build, so it's not even really a great work-around. At this point, we're just not going to use the plugin (we were only enforcing java version and maven version, so it's not a big loss anyway).
> 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
[jira] Commented: (MENFORCER-14) Enforcer Plugin Messes Up
Dependencies
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Closed: (MENFORCER-14) Enforcer Plugin Messes Up
Dependencies
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed MENFORCER-14.
------------------------------
Resolution: Duplicate
This is a duplicate of MENFORCER-11. The fix is easy, change enforce-once to enforce.
Also, I noticed in one of your poms that you use ${project.version} This can cause subtle problems and you are better off defining a property in a parent and using that (because the property won't change until you change it by hand) The issue is here:MNG-2486
> 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