Thank you Rene for answer, partially yes I’m trying to prepare a plugin which will be on one hand facade for sonar plugin and hide complexity of it’s configuration, and from the other hand run different other tools like jstestdriver from within, I need to serve 4 languages java, javascript, c#, cpp, project contains many subprojects some of them contain 2 from 4 aforementioned languages. Moreover copy a few files, change other (configs). For javascript I will use standalone sonar-runner because I couldn’t make sonar - plugin work properly with code coverage data for javascript. I have one more
idea why it fails maybe proper set of working directory would help or maybe not. In the end it works smoothly with sonar-runner. One goal of my custom plugin is prepare DSL with one main closure containing sections for all languages.
“Maybe a better approach to customize the build-in Sonar plugin is to configure different instances of the SonarAnalyze in your plugin.” - could you write more about it? how to achieve it programatically? normally I would use task name1(type: SonarAnalyze), task name2(type: SonarAnalyze) and so on… am I right?