On Mar 20, 2007, at 5:14 AM, Brian E. Fox wrote:
Come, on - enforcer:enforce just sounds cool.
Ya, but its not terribly descriptive :-P
I actually started in this direction, and the code to check both
versions was nearly identical. After I thought about it for a while, I
thought that these two where likely to be used very frequently
together.
Instead of forcing someone to bind the plugin to two executions, it
made
sense to combine them into a single goal. OS was different enough that
it belongs separate.
Personally I have not problem adding extra execution per thing I want
to enforce. IMO that is much clearer and simplifies the implementing
mojo.
If you feel strongly enough about the name, I'm not particularly
tied to
it...just like the way it sounds.
For the version range syntax, I put some thought into this one. I
decided that good or bad, someone using Maven would more likely be
familiar with the current range syntax than something else. This
turned
out to be a major PITA because it didn't work right out of the box due
to various implementation quirks. I'm open to other solutions, but I
still maintain that consistency is best for the users so they don't
have
to learn multiple range specifications. I know that there is a
proposal
out there to replace the range handling in maven, and I would expect
this plugin to be updated to handle new specifications as well to
match
maven.
Funny... most folks I know don't use version ranges. We (geronimo)
tried to use them at one point for our specs, but key plugins (like
the idea plugin) don't support it.
I don't think that most folks using M2 are familiar with ranges...
nor do they use them... and when those who do use them... usually
tend to find out they don't work so well.
The OS stuff falls into the same boat, why reinvent a syntax when one
already exists?
Ya, I hear ya... it was just a comment... and more about how the
range syntax hurts my brain more than anything ;-) Just looking at a
range its not really easy to tell what it means... where IMO the 1.0+
and 1.0* syntax is relatively clear w/o having to go read a syntax
mapping table ;-)
--jason
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
