Thank you Stephen. So as Robert recommended, I will drop the release and change the issueManagement section after the vote.
On Tue, Nov 1, 2011 at 12:01 PM, Stephen Connolly < [email protected]> wrote: > http://jira.codehaus.org/browse/MSONAR > > On 31 October 2011 20:15, Olivier Lamy <[email protected]> wrote: > > 2 * +1 > > > > 2011/10/31 Simon Brandhof <[email protected]>: > >> Hi there, > >> > >> The sonar mojo is still a beta version but it's used in production for a > >> long time (a few years). For this reason I think it deserves to upgrade > to > >> versions 1.0 (for maven 2) and 2.0 (for maven 3). > >> A few issues have been resolved since last release, particularly the > >> possible conflict of commons-lang with some sonar plugins (see > MOJO-1763). > >> > >> Release 2.0 for maven 3 : > >> > >> Release notes : > >> > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11062&version=18040 > >> Staging repository : > >> https://nexus.codehaus.org/content/repositories/orgcodehausmojo-023/ > >> > >> Release 1.0 for maven 2 : > >> > >> Release notes : > >> > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11062&version=18041 > >> Staging repository : > >> https://nexus.codehaus.org/content/repositories/orgcodehausmojo-024/ > >> > >> About the release process, docck:check is ok but I didn't create the > >> dedicated JIRA project. It still uses the component "sonar" in the Mojo > >> project. Is it blocker ? If yes, can an administrator create it please ? > > IMHO not blocker, let's push release, make users happy and do > > administrative tasks after (as they can take long due to we depends on > > codehaus admin folks spare time). > > Once is done republish the web site with fixed informations. > >> > >> The vote is open. > >> > >> Thanks > >> > >> Simon Brandhof > >> www.sonarsource.com > >> twitter.com/SimonBrandhof > >> > > > > > > > > -- > > Olivier Lamy > > Talend : http://talend.com > > http://twitter.com/olamy | http://linkedin.com/in/olamy > > > > --------------------------------------------------------------------- > > To unsubscribe from this list, please visit: > > > > http://xircles.codehaus.org/manage_email > > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
