Re: [mojo-dev] Re: [VOTE] Release the retrotranslator-maven-plugin

[Jason Dillon <ja...@planet57.com>]

On Sep 12, 2006, at 3:49 PM, dan tran wrote:
> 2 scenarios:
>
>    1 - user uses version 1, then he/she will need to fix up lots of  
> configurations in order to use 1.1

Yes, I don't see this as a major problem.  If a user wants to use the  
new functionality they need to upgrade their configuration anyways.


>    2. user does not specify plugin in pom.  when 1.1 comes out,  
> maven pick up the latest and
>        user build fails

The maven-surefire-plugin has already done this... which has  
convinced me that I always need to specify the version... a few  
others too have released plugins that cause builds to break, so I'm  
not sure that this is really a big deal.  I also read some notes  
about the assembly plugin changing to include non-backwards  
compatible changes...


>  Please ping maven dev for plugin backward compatibitly policy.

Its more of a huge problem to ensure backwards compatibility between  
significant plugin changes.  I am fine to keep changes in groups  
compatible, say all 1.x versions and then all 2.x and so on, but  
keeping 1.x and 2.x compatible is a massive pain, and only ends up  
causing plugin developers and users confusion.

This seems like a really artificial requirement.

--jason

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