On 04/09/2007, at 11:52 AM, Brian E. Fox wrote:
I have a few problems I need to work through before the next enforcer
release.
First is that the enforce-once mojo declares @aggregator but still
executes for all children. (MENFORCER-12) Is this a bug in maven or
are
aggregators still supposed to be inherited and executed?
Sounds like a bug to me... is it better to just cache the result as
the meaning of "once" instead of worrying about how many times Maven
runs it?
The next one is sorta related to the first. I've added some rules that
require dependency resolution. Since there's currently no easy way to
resolve dependencies inside the mojo besides
@requiresDependencyResolution, I just set that. Unfortunately the
combination of aggregator and dependencyResolution is broken in maven
and causes all kinds of havoc (MNG-2277 / MENFORCER-11). One way I
thought to work around this is to make another enforcer goal like
enforce:dependencies and then allow the rules to declare they need
dependencies resolved and then warn and skip if they are configured to
execute inside the regular enforce-once goal. This workaround seems
kinda lame but even fixing MNG-2277 in 2.0.8 means it's still
broken for
those with older versions which isn't good either. Suggestions?
Yeah, unfortunately I think you might need to work around it...
though having a dependencies goal does seem lame. Would changing the
behaviour of enforce-once to not need the @aggregator be better?
- Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
