IMV the plugin shouldn't assert a particular workflow, at least not without a simple switch to remove that dependency. I say this partly because the workflow it asserts is one that I will have to write code to override & I don't think I am doing anything particularly unusual.
To give a concrete example.... My build system is driven by teamcity and relies on teamcity build chains. Each component (releaseable thing) is pushed through 3 stages which are basically unit test - integration test - analyse. Each stage is a separate build linked via a snapshot dependency. A component can depend on other components but they never depend on a successful analyse (for various reasons, mainly that static analysis is too riddled with false positives to be a hard dependency). The data sonar needs (i.e. the jacoco coverage stats) is therefore pushed forward from build to build using teamcity artefact dependencies & our analyse build is a gradlew assemble sonarAnalyze Cheers Matt -- View this message in context: http://gradle.1045684.n5.nabble.com/SonarRunner-Task-Dependencies-tp5711079p5711086.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
