>What you're saying sounds reasonable, I agree. Still waiting for
>Enforcer 1.0 release to take advantage of requirePluginVersions,
>though :-) Any updates, Brian?
No, sorry. I am unable to replicate the issue I saw once at a customer
site, so I might just move forward with another beta release.
>Whenever version ranges were mentioned in
>Mavenland it stated that a plain version was a recommendation, while a
>plain version surrounded by brackets was a requirement ("locked down"
>version). From my tiny experiment here, and people's responses, I take
>it that just a plain version will achieve what I want for plugins.
This is true for dependencies because of the transitivity. Plugins are
not transitive in the same way, so there's no need for ranges...in fact
I'm not sure what happens if you use a range for a plugin, never thought
about it before.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
