Hi, personally I like to separate things and wouldn't want to launch
mvn sonar:sonar manually, therefore I preferred the script integration as said in the Travis docs. I'm not quite sure if Fabrice has the same understanding of the issues I encountered while trying to work on a sonar integration. Yesterday's status was: * Travis builds are green * Travis starts the sonar-scanner .... Cheers, Phil Am 24.04.19 um 18:36 schrieb acob...@apache.org: > This is an automated email from the ASF dual-hosted git repository. > > acoburn pushed a commit to branch more_sonar_updates > in repository https://gitbox.apache.org/repos/asf/incubator-tamaya.git > > commit 71888dac3a5c5715116f248ba8f2947b3947f78f > Author: Aaron Coburn <acob...@apache.org> > AuthorDate: Wed Apr 24 12:35:39 2019 -0400 > > Sonar configuration updates > > More sonar updates > --- > .travis.yml | 6 +----- > 1 file changed, 1 insertion(+), 5 deletions(-) > > diff --git a/.travis.yml b/.travis.yml > index 0a9639a..ee0c094 100644 > --- a/.travis.yml > +++ b/.travis.yml > @@ -6,15 +6,11 @@ addons: > sonarcloud: > organization: "apache" > > -script: > - - sonar-scanner > - > jobs: > include: > - name: "Java 8" > jdk: openjdk8 > - # script: mvn clean install sonar:sonar > -Dsonar.organization=apache -Dsonar.projectKey=apache_incubator-tamaya > -Dsonar.host.url="https://sonarcloud.io" -Dsonar.login="$SONAR_TOKEN" > - script: mvn clean install > + script: mvn clean install sonar:sonar -Dsonar.organization=apache > -Dsonar.projectKey=apache_incubator-tamaya > > - name: "Java 9" > jdk: openjdk9 >