You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Fox (JIRA)" <ji...@codehaus.org> on 2007/07/13 04:31:13 UTC
[jira] Created: (MENFORCER-11) enforce-once causes MNG-2277 to be
expressed in reactor builds. Find a way to work around it.
enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it.
---------------------------------------------------------------------------------------------
Key: MENFORCER-11
URL: http://jira.codehaus.org/browse/MENFORCER-11
Project: Maven 2.x Enforcer Plugin
Issue Type: Improvement
Components: Plugin
Affects Versions: 1.0-alpha-3
Reporter: Brian Fox
Assignee: Brian Fox
In 1.0-alpha-3, the enforce goal now requires dependency resolution to support the new dependency rules (noSnapshots, noBannedDependencies). Because enforce-once extends and adds as an aggregator, this causes the maven bug to appear. The work around for now is to use enforce not the enforce-once goal (the aggregator part of enforce-once doesn't work anyway).
The fix would be to resolve the dependencies manually in the plugin or to make a new mojo that requires dependency resolution and put enforce and enforce-once back the way they where.
--
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] Updated: (MENFORCER-11) enforce-once causes MNG-2277 to be
expressed in reactor builds. Find a way to work around it.
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox updated MENFORCER-11:
-------------------------------
Description:
In 1.0-alpha-3, the enforce goal now requires dependency resolution to support the new dependency rules (noSnapshots, noBannedDependencies). Because enforce-once extends and adds as an aggregator, this causes the maven bug MNG-2277 to appear. The work around for now is to use enforce not the enforce-once goal (the aggregator part of enforce-once doesn't work anyway).
The fix would be to resolve the dependencies manually in the plugin or to make a new mojo that requires dependency resolution and put enforce and enforce-once back the way they where.
was:
In 1.0-alpha-3, the enforce goal now requires dependency resolution to support the new dependency rules (noSnapshots, noBannedDependencies). Because enforce-once extends and adds as an aggregator, this causes the maven bug to appear. The work around for now is to use enforce not the enforce-once goal (the aggregator part of enforce-once doesn't work anyway).
The fix would be to resolve the dependencies manually in the plugin or to make a new mojo that requires dependency resolution and put enforce and enforce-once back the way they where.
> enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it.
> ---------------------------------------------------------------------------------------------
>
> Key: MENFORCER-11
> URL: http://jira.codehaus.org/browse/MENFORCER-11
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Improvement
> Components: Plugin
> Affects Versions: 1.0-alpha-3
> Reporter: Brian Fox
> Assignee: Brian Fox
>
> In 1.0-alpha-3, the enforce goal now requires dependency resolution to support the new dependency rules (noSnapshots, noBannedDependencies). Because enforce-once extends and adds as an aggregator, this causes the maven bug MNG-2277 to appear. The work around for now is to use enforce not the enforce-once goal (the aggregator part of enforce-once doesn't work anyway).
> The fix would be to resolve the dependencies manually in the plugin or to make a new mojo that requires dependency resolution and put enforce and enforce-once back the way they where.
--
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-11) enforce-once causes MNG-2277 to be
expressed in reactor builds. Find a way to work around it.
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114023 ]
Brian Fox commented on MENFORCER-11:
------------------------------------
It should go out for vote in a few days. You can try the RC at http://people.apache.org/~brianf/2.0.8
> enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it.
> ---------------------------------------------------------------------------------------------
>
> Key: MENFORCER-11
> URL: http://jira.codehaus.org/browse/MENFORCER-11
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Improvement
> Components: Plugin
> Affects Versions: 1.0-alpha-3
> Reporter: Brian Fox
> Assignee: Brian Fox
> Fix For: 1.0
>
>
> In 1.0-alpha-3, the enforce goal now requires dependency resolution to support the new dependency rules (noSnapshots, noBannedDependencies). Because enforce-once extends and adds as an aggregator, this causes the maven bug MNG-2277 to appear. The work around for now is to use enforce not the enforce-once goal (the aggregator part of enforce-once doesn't work anyway).
> The fix would be to resolve the dependencies manually in the plugin or to make a new mojo that requires dependency resolution and put enforce and enforce-once back the way they where.
--
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-11) enforce-once causes MNG-2277 to be
expressed in reactor builds. Find a way to work around it.
Posted by "Damien Lecan (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107939 ]
Damien Lecan commented on MENFORCER-11:
---------------------------------------
Multi-module project build doesn't work anymore with alpha-3 for my projects (between 10 and 40 modules)
alpha-2 is working fine
> enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it.
> ---------------------------------------------------------------------------------------------
>
> Key: MENFORCER-11
> URL: http://jira.codehaus.org/browse/MENFORCER-11
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Improvement
> Components: Plugin
> Affects Versions: 1.0-alpha-3
> Reporter: Brian Fox
> Assignee: Brian Fox
>
> In 1.0-alpha-3, the enforce goal now requires dependency resolution to support the new dependency rules (noSnapshots, noBannedDependencies). Because enforce-once extends and adds as an aggregator, this causes the maven bug MNG-2277 to appear. The work around for now is to use enforce not the enforce-once goal (the aggregator part of enforce-once doesn't work anyway).
> The fix would be to resolve the dependencies manually in the plugin or to make a new mojo that requires dependency resolution and put enforce and enforce-once back the way they where.
--
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-11) enforce-once causes MNG-2277 to be
expressed in reactor builds. Find a way to work around it.
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103457 ]
Brian Fox commented on MENFORCER-11:
------------------------------------
I don't see how it's any different. The enforce-once goal still doesn't work correctly and executes again for every project anyway. (MENFORCER-12)
> enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it.
> ---------------------------------------------------------------------------------------------
>
> Key: MENFORCER-11
> URL: http://jira.codehaus.org/browse/MENFORCER-11
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Improvement
> Components: Plugin
> Affects Versions: 1.0-alpha-3
> Reporter: Brian Fox
> Assignee: Brian Fox
>
> In 1.0-alpha-3, the enforce goal now requires dependency resolution to support the new dependency rules (noSnapshots, noBannedDependencies). Because enforce-once extends and adds as an aggregator, this causes the maven bug MNG-2277 to appear. The work around for now is to use enforce not the enforce-once goal (the aggregator part of enforce-once doesn't work anyway).
> The fix would be to resolve the dependencies manually in the plugin or to make a new mojo that requires dependency resolution and put enforce and enforce-once back the way they where.
--
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-11) enforce-once causes MNG-2277 to be
expressed in reactor builds. Find a way to work around it.
Posted by "Andrew Perepelytsya (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103455 ]
Andrew Perepelytsya commented on MENFORCER-11:
----------------------------------------------
This is not really a workaround. We have around 90 modules now and using enforce instead of enforce-once simply kills the build making it unusable.
> enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it.
> ---------------------------------------------------------------------------------------------
>
> Key: MENFORCER-11
> URL: http://jira.codehaus.org/browse/MENFORCER-11
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Improvement
> Components: Plugin
> Affects Versions: 1.0-alpha-3
> Reporter: Brian Fox
> Assignee: Brian Fox
>
> In 1.0-alpha-3, the enforce goal now requires dependency resolution to support the new dependency rules (noSnapshots, noBannedDependencies). Because enforce-once extends and adds as an aggregator, this causes the maven bug MNG-2277 to appear. The work around for now is to use enforce not the enforce-once goal (the aggregator part of enforce-once doesn't work anyway).
> The fix would be to resolve the dependencies manually in the plugin or to make a new mojo that requires dependency resolution and put enforce and enforce-once back the way they where.
--
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-11) enforce-once causes MNG-2277 to be
expressed in reactor builds. Find a way to work around it.
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114024 ]
Brian Fox commented on MENFORCER-11:
------------------------------------
I got the issues confused, the enforcer plugin should be out very shortly as well.
> enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it.
> ---------------------------------------------------------------------------------------------
>
> Key: MENFORCER-11
> URL: http://jira.codehaus.org/browse/MENFORCER-11
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Improvement
> Components: Plugin
> Affects Versions: 1.0-alpha-3
> Reporter: Brian Fox
> Assignee: Brian Fox
> Fix For: 1.0
>
>
> In 1.0-alpha-3, the enforce goal now requires dependency resolution to support the new dependency rules (noSnapshots, noBannedDependencies). Because enforce-once extends and adds as an aggregator, this causes the maven bug MNG-2277 to appear. The work around for now is to use enforce not the enforce-once goal (the aggregator part of enforce-once doesn't work anyway).
> The fix would be to resolve the dependencies manually in the plugin or to make a new mojo that requires dependency resolution and put enforce and enforce-once back the way they where.
--
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-11) enforce-once causes MNG-2277 to be
expressed in reactor builds. Find a way to work around it.
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed MENFORCER-11.
------------------------------
Resolution: Fixed
Fix Version/s: 1.0
Enforce-once has the @aggregator removed and is now deprecated.
Unfortunately, in Maven, the @aggregator only applies to command line invocation and has no real effect when bound to a pom (at least not the run once desired effect).
In the future, I may add caching to the rules to allow things to run once, but the plugin will still execute for all children. A rule will need to declare if it is safe to cache or not.
> enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it.
> ---------------------------------------------------------------------------------------------
>
> Key: MENFORCER-11
> URL: http://jira.codehaus.org/browse/MENFORCER-11
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Improvement
> Components: Plugin
> Affects Versions: 1.0-alpha-3
> Reporter: Brian Fox
> Assignee: Brian Fox
> Fix For: 1.0
>
>
> In 1.0-alpha-3, the enforce goal now requires dependency resolution to support the new dependency rules (noSnapshots, noBannedDependencies). Because enforce-once extends and adds as an aggregator, this causes the maven bug MNG-2277 to appear. The work around for now is to use enforce not the enforce-once goal (the aggregator part of enforce-once doesn't work anyway).
> The fix would be to resolve the dependencies manually in the plugin or to make a new mojo that requires dependency resolution and put enforce and enforce-once back the way they where.
--
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-11) enforce-once causes MNG-2277 to be
expressed in reactor builds. Find a way to work around it.
Posted by "Jorg Heymans (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114013 ]
Jorg Heymans commented on MENFORCER-11:
---------------------------------------
I just spent a good few hours tracking down the weirdest build errors in our project due to this bug. When is the next release scheduled for ?
> enforce-once causes MNG-2277 to be expressed in reactor builds. Find a way to work around it.
> ---------------------------------------------------------------------------------------------
>
> Key: MENFORCER-11
> URL: http://jira.codehaus.org/browse/MENFORCER-11
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Improvement
> Components: Plugin
> Affects Versions: 1.0-alpha-3
> Reporter: Brian Fox
> Assignee: Brian Fox
> Fix For: 1.0
>
>
> In 1.0-alpha-3, the enforce goal now requires dependency resolution to support the new dependency rules (noSnapshots, noBannedDependencies). Because enforce-once extends and adds as an aggregator, this causes the maven bug MNG-2277 to appear. The work around for now is to use enforce not the enforce-once goal (the aggregator part of enforce-once doesn't work anyway).
> The fix would be to resolve the dependencies manually in the plugin or to make a new mojo that requires dependency resolution and put enforce and enforce-once back the way they where.
--
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