Hi Simon,
Last week I've asked Juven Xu to prepare the nexus repository of codehaus for staging and deploying the mojo projects[1] He has finished his part, so now it's up to us to finalize our part[2] So before you can deploy the sonar-m-p, I think we have to update the mojo-parent[3], which requires a vote as well. I'd hoped one of the despots or someone with staging experience could pick up MOJO-1553. We just have to make sure everyone is informed correctly, not just by some wild guesses from me because the docs say so. This shouldn't be a problem, it's just about finding the right person who wants to do this. - Robert [1] http://jira.codehaus.org/browse/HAUS-2000 [2] http://jira.codehaus.org/browse/MOJO-1553 [3] http://docs.codehaus.org/display/HAUSMATES/Codehaus+Maven+Repository+Usage+Guide#CodehausMavenRepositoryUsageGuide-6.POMandsettingsconfig From: [email protected] Date: Mon, 30 Aug 2010 17:03:46 +0200 To: [email protected] Subject: [mojo-dev] [VOTE] Sonar maven plugin 1.0-beta-2 Hi everyone, This new version makes sonar configuration easier when using a maven proxy like Nexus or Archiva. Indeed no additional settings are required anymore ! Let's remind that the current version 1.0-beta-1 needs to declare a mirror in maven settings (see the section "declare the maven internal repository into Nexus"). This improvement requires Sonar 2.2+. It is automatically disabled when using sonar 2.1 or less. The snapshot has been deployed. Release notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11062&version=16625 The vote is open for 72 hours with a lazy consensus as usual. Thanks Simon Brandhof SonarSource.org SonarSource.com ---
