On 15/09/2013, at 10:18 PM, Szczepan Faber <szczepan.fa...@gradleware.com> wrote:
> I would be fine with promoting it as is. IMHO, existence of known problems > should not make the feature kept in incubating mode for too long. If the > decision is to wait, I'm fine with that, too :) The question is whether we consider #1 a breaking change. If so, we should fix it before we promote the plugin. > > Cheers! > > > On Sun, Sep 15, 2013 at 8:49 AM, Peter Niederwieser <pnied...@gmail.com> > wrote: > I'd consider fixing the following two issues before promoting the plugin: > > 1. The new plugin makes the `SonarRunner` task depend on `Test` tasks. This > means that whenever a test fails, Sonar analysis doesn't take place. Not > sure if there is a JIRA for this. > > 2. GRADLE-2817 > > Cheers, > Peter > > > Adam Murdoch wrote > > Any know of a reason why we should not promote the sonar-runner plugin > > from incubating, and deprecate the sonar plugin? > > > > > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/promoting-sonar-runner-plugin-tp5711817p5711855.html > Sent from the gradle-dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > > > -- > Szczepan Faber > Principal engineer@gradle; Founder@mockito > Join me at the Gradle eXchange 2013, Oct 28th in London: > http://skillsmatter.com/event/java-jee/gradle-exchange-2013 -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com Join us at the Gradle eXchange 2013, Oct 28th in London, UK: http://skillsmatter.com/event/java-jee/gradle-exchange-2013
