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

Compatibility is broken with SonarQube 7.6 #25

Closed
varrocen opened this Issue Feb 8, 2019 · 5 comments

Comments

Projects
3 participants
@varrocen
Copy link

varrocen commented Feb 8, 2019

I have upgrade my SonarQube to 7.6 and now I have an error when I scan my project:

ERROR: Error during SonarQube Scanner execution
ERROR: ch.devcon5.sonar.plugins.mutationanalysis.sensors.PitestSensor has unsatisfied dependency 'class org.sonar.api.profiles.RulesProfile' for constructor 'public ch.devcon5.sonar.plugins.mutationanalysis.sensors.PitestSensor(org.sonar.api.config.Configuration,org.sonar.api.profiles.RulesProfile,org.sonar.api.batch.fs.FileSystem)' from org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer@55b62629:45<[Immutable]:org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer@6c2c1385:353<[Immutable]:org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer@585ac855:39<|
@gmuecke

This comment has been minimized.

Copy link
Member

gmuecke commented Feb 8, 2019

Hi varrocen, thank you for reporting. I can reproduce & confirm the issue and will work on a fix in the next days.

@gmuecke gmuecke added the bug label Feb 8, 2019

@gmuecke gmuecke added this to To do in Release 1.4 via automation Feb 8, 2019

@gmuecke gmuecke self-assigned this Feb 8, 2019

gmuecke added a commit that referenced this issue Feb 10, 2019

gmuecke added a commit that referenced this issue Feb 10, 2019

@gmuecke

This comment has been minimized.

Copy link
Member

gmuecke commented Feb 10, 2019

It seemed, other plugins had similar issues with the RulesProfile dependency.

Solution would be to use the ActiveRules instead. I tried it locally, looks promising. But I need some more tests. But I'm positive I can provide a fix beginning of the upcoming week.

@gmuecke gmuecke moved this from To do to In progress in Release 1.4 Feb 10, 2019

gmuecke added a commit that referenced this issue Feb 11, 2019

gmuecke added a commit that referenced this issue Feb 11, 2019

@gmuecke gmuecke moved this from In progress to Done in Release 1.4 Feb 11, 2019

@varrocen

This comment has been minimized.

Copy link
Author

varrocen commented Feb 11, 2019

Hi ! Thank you for your fix.

@abego

This comment has been minimized.

Copy link

abego commented Feb 17, 2019

I saw you put the issue in Done in Release 1.4. When do you plan to do the release/publish it?

@gmuecke

This comment has been minimized.

Copy link
Member

gmuecke commented Feb 17, 2019

@gmuecke gmuecke closed this Feb 18, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment