-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't enable groovy files analysis #78
Comments
Hi, |
@pucii |
Can groovy files be analysed with the maven plugin? You could try to use the Sonar Scanner cli instead. |
It can't |
Is there a solution to this issue ? |
The new release 1.6 should support all recent SonarQube versions. If you still see this issue, please report it on the new project |
I have a maven project with groovy and java files. I ran SonarQube analyses for the project on SonarQube server when the Groovy plugin was not installed yet. Then with Groovy plugin installed, I added empty sonar-project.properties file to my project. And also
<sonar.groovy.binaries>target/classes</sonar.groovy.binaries>
to my pom file. Then I ran Jenkins jobwith a build step
$SONAR_MAVEN_GOAL -Dsonar.host.url=$SONAR_HOST_URL
and pre-build stepclean package -Dmaven.test.skip=true
.The problem is that I still don't see any .groovy files on my Sonar project, which was created during the first run.
The text was updated successfully, but these errors were encountered: