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
