Hi Brian, On Jan 10, 2008 5:40 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > The enforcer plugin requirePluginVersions rule intentionally scans > everything in your pom inheritance to see anything that isn't defined. > This also includes things you haven't declared but are being used by the > standard lifecycle (compile,install etc etc). The alternative is that > everytime you tried something new, it would complain about the version.
That's fine with me, like I said, I have to specify those versions anyway. It just surprised me a bit. > It also doesn't care if the profile is active or not, if you declare a > plugin without a version anywhere...the enforcer will punch you in the > face. Yes, but what I don't understand is why I'm being punched in the face when I've specified the version twice ... but in the profile. :-) And it's complaining about its *own* version. Which, again, I *have* specified. > There is one known issue right now and that's when you run mvn site. It > gets confused because mvn injects the reporting plugins into the project > as plugins and since I'm not currently scanning the reporing > declarations, it incorrectly says they aren't locked down. Once I get > time to fix this, I'll be putting out 1.0. Mmmmh, I didn't run into this when running mvn site? Cheers, Hilco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
