Or just switch to "enforce" instead of "enforce-once". As noted in the issue, the aggregator portion of enforce-once isn't working (never has) so the two goals are effectively the same in terms of performance. (enforce-once runs on each child, the intent is for it to just run once)
-----Original Message----- From: Tomislav Stojcevich [mailto:[EMAIL PROTECTED] Sent: Monday, August 13, 2007 2:15 PM To: Maven Users List Subject: Re: [m2] urgent issue with modules and sub-modules for initial builds The real solution is reverting to the enforcer 1.0-alpha-2 release. I was using 1.0-alpha-3 which for some reason isn't listed as the current release. The JIRA for the bug in question is http://jira.codehaus.org/browse/MENFORCER-14 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
