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]
