As 3) in practice/runtime will be the version of Maven used, I'd say that 2) and 3) always should be the same. Or?
/Anders On Thu, Jan 13, 2011 at 21:13, Paul Gier <pg...@redhat.com> wrote: > On 01/13/2011 10:22 AM, Benjamin Bentmann wrote: > > Paul Gier wrote: > > > >> But I thought the<prerequisite> has a somewhat different meaning. > >> That's the minimum version of Maven used to build the project > > > > The <prerequisite> tag has unfortunately an overloading meaning. Going > > forward, use it only to declare the runtime prerequisites for Maven > > plugins and use the Enforcer Plugin to check buildtime constraints. > > > > > > Benjamin > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > So, in general a property called something like "maven.version" might > have one of three different meanings. > > 1. Maven version required to build the project - Handled by enforcer > > 2. Maven version required at runtime for a plugin to be used - Handled > by prereq tag > > 3. Version of maven components used as dependencies > > It seems that each of these could contain a different value. Getting > back to the original question, only number 3 is relevant for building > the javadocs. So what's the best way to include that in a standard way? > Using the prerequisites tag as Robert suggested seems incorrect since > it can be different than the components version. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
