I'm +1 on removing the "version" attribute requirement. -----Original Message----- From: Knut Wannheden [mailto:[EMAIL PROTECTED] Sent: Monday, March 20, 2006 2:47 AM To: [email protected] Subject: Re: Scrap module version?
I agree. We could never quite agree on how the version matching should be specified so the only policy supported by <dependency> is "exact version". However I don't think I've ever used it. So +1 on making the version attribute at least optional. --knut On 3/19/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > It's beginning to feel to me like HiveMind module version is redundant > with a reasonable Maven 2 build (and I think most Java software will > build with Maven 2 in the near future, or Ant using Ivy). > > We never implemented reasonable checks that the version matches > expectations; just that a version is provided and fits a (very > limited) format. I had originally wanted the <dependency> element to > handle this, with partial version matching. > > Nowadays, my "less is more" philosophy says the version number > matching falls under the YAGNI category. Possibly <dependency> as > well. > > Thoughts? > > -- > Howard M. Lewis Ship > Independent J2EE / Open-Source Java Consultant > Creator, Jakarta Tapestry > Creator, Jakarta HiveMind > > Professional Tapestry training, mentoring, support > and project work. http://howardlewisship.com > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
