But I thought the <prerequisite> has a somewhat different meaning.
That's the minimum version of Maven used to build the project which is
often different than the versions of dependencies on maven-artifact or
other jars. For example, I may be able to build a plugin using Maven
2.0.10, but I want some features available in newer apis only available
in 2.2.1 jars, so my ${mavenVersion} property might be different than
the value in the prerequisite tag.
On 01/12/2011 01:56 PM, Robert Scholte wrote:
> Most of the mojo-projects are starting to use a property for the maven
> version, but I've noticed both ${mavenVersion} and ${maven.version}.
> If you use such a property, you would always set the prerequisite of
> Maven for that project too.
> So I'd prefer to use ${project.prerequisite.maven}, since it doesn't
> matter if the project using the mojo-parent uses properties or not.
>
> -Robert
>
>> Date: Wed, 12 Jan 2011 17:46:49 +0100
>> From: denn...@apache.org
>> To: dev@mojo.codehaus.org
>> Subject: Re: [mojo-dev] Redirect errors for some old Maven API docs
> urls when creating mojo site javadoc
>>
>> On 2011-01-12 12:21, Benjamin Bentmann wrote:
>> > Paul Gier wrote:
>> >
>> >> This seems like a good use case for having a property available
>> >> containing the current Maven version (MNG-4112). Then we could just
>> >> substitute something like ${maven.version} for "current".
>> >
>> > Having the javadoc links depend on the Maven version currently used to
>> > build is a bad idea as it makes the build/site completely dependent on
>> > the build environment.
>> >
>> > IMHO the javadoc links should match the dependencies the plugin was
>> > compiled against so Robert's suggestion to use a property seems more
>> > sensible to me.
>>
>> Over at the Apache Maven project we often set a property in the POM
>> called mavenVersion. That is then used for both prerequisites.maven and
>> the dependencies on Maven core artifacts. If we do so here, we could use
>> that parameter for the Javadoc links. We could put a default value for
>> it in the parent POM to make sure that it is always present.
>>
>> >
>> >
>> > Benjamin
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe from this list, please visit:
>> >
>> > http://xircles.codehaus.org/manage_email
>> >
>> >
>> >
>>
>>
>> --
>> Dennis Lundberg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
