I've got two questions: "Maven 2 users will be automatically downgraded to version 1.0-beta-2" Is this really what we want? A user defines a version of the plugin, but because he's using an older version of Maven he's getting an older version through some 'magic'. I don't think we should use this kind of 'automagic'. Why not just fail with the right message and keep the user in control? The other question is more of a general thing for mojo's: Up untill now we tried to keep the required Maven-version as low as possible so we can serve as much projects as possible. I don't think this should change with the release of Maven3. Of course we should encourage people to use the latest Maven-version, but companies can have strict policies about updating sofware. A maven-plugin is often much easier to upgrade than Maven itself, especially in huge DTAP systems. IMHO I think we still should try to keep the required Maven version as low as possible, but it should also be able to run with Maven3. If a project requires Maven3 to run with Maven3, we'll, than Maven3 is the lowest possible version. (maybe we should fork this to a separate thread...) - Robert
From: [email protected] Date: Thu, 11 Nov 2010 12:50:39 +0100 To: [email protected] Subject: [mojo-dev] [VOTE] Sonar Maven Plugin 2.0-beta-1 Hi, This release adds maven 3 support (see http://jira.codehaus.org/browse/MOJO-1545). Maven 2 users will be automatically downgraded to version 1.0-beta-2 and should not be impacted. The staged repository is : https://nexus.codehaus.org/content/repositories/orgcodehausmojo-020/ Site has been deployed : http://mojo.codehaus.org/sonar-maven-plugin/ Testing this version requires Sonar 2.4-RC1 : http://dist.sonar.codehaus.org/sonar-2.4-RC1.zip. The plugin explicitly fails if a lesser version of Sonar is used. The vote is open for 72 hours and will succeed by lazy consensus. Thanks Simon
