Change release announcement template?

[dfabulich]

The release announcement template is here:
http://maven.apache.org/developers/release/releasing.html

It currently says:

> You can run mvn -up to get the latest version of the plugin, or specify
> the version in your project's plugin configuration:
>
> <plugin>
>  <groupId>org.apache.maven.plugins</groupId>
>  <artifactId>maven-XXX-plugin</artifactId>
>  <version>Y.Z</version>
> </plugin>

... but that's not true any more, is it?  In Maven 2.0.9, running -up
won't give you Surefire 2.4.3; you'll be stuck on Surefire 2.4.2.  (and
that's a good thing!)

Unfortunately, the new version of Surefire requires Maven 2.0.6 or higher
(for toolchain support), so users of Maven 2.0.0-2.0.5 have no way to
upgrade to Surefire 2.4.3; users of 2.0.6-2.0.8 will be auto-upgraded (and
can force an auto-upgrade with -up) and users of 2.0.9 will have to
specify the version explicitly.

I don't want to say all that in the release announcement template, right?
I think it should just say something like this, omitting discussion of
"-up":

> You can specify the plugin version in your project's plugin
> configuration:
>
> <plugin>
>  <groupId>org.apache.maven.plugins</groupId>
>  <artifactId>maven-XXX-plugin</artifactId>
>  <version>Y.Z</version>
> </plugin>

I'll just say something like that in the Surefire announcment I'm going to
make in a few minutes; if people like this wording, I'll modify the
template in the documentation.

-Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[brettporter]

+1

I think the section below in combination with "requires Maven 2.0.6 or  
greater" works.

- Brett

On 15/05/2008, at 10:20 AM, Dan Fabulich wrote:

>
> The release announcement template is here:
> http://maven.apache.org/developers/release/releasing.html
>
> It currently says:
>
>> You can run mvn -up to get the latest version of the plugin, or  
>> specify the version in your project's plugin configuration:
>>
>> <plugin>
>> <groupId>org.apache.maven.plugins</groupId>
>> <artifactId>maven-XXX-plugin</artifactId>
>> <version>Y.Z</version>
>> </plugin>
>
> ... but that's not true any more, is it?  In Maven 2.0.9, running -
> up won't give you Surefire 2.4.3; you'll be stuck on Surefire  
> 2.4.2.  (and that's a good thing!)
>
> Unfortunately, the new version of Surefire requires Maven 2.0.6 or  
> higher (for toolchain support), so users of Maven 2.0.0-2.0.5 have  
> no way to upgrade to Surefire 2.4.3; users of 2.0.6-2.0.8 will be  
> auto-upgraded (and can force an auto-upgrade with -up) and users of  
> 2.0.9 will have to specify the version explicitly.
>
> I don't want to say all that in the release announcement template,  
> right? I think it should just say something like this, omitting  
> discussion of "-up":
>
>> You can specify the plugin version in your project's plugin  
>> configuration:
>>
>> <plugin>
>> <groupId>org.apache.maven.plugins</groupId>
>> <artifactId>maven-XXX-plugin</artifactId>
>> <version>Y.Z</version>
>> </plugin>
>
> I'll just say something like that in the Surefire announcment I'm  
> going to make in a few minutes; if people like this wording, I'll  
> modify the template in the documentation.
>
> -Dan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

--
Brett Porter
brett@...
http://blogs.exist.com/bporter/


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...