Aman Sharma

@khaes-kth @monperrus I think we can focus on this issue before adding any further rules.

@monperrus I will report this to SonarJava and then we can surely confirm if the issue is at our end or theirs. Then we can take the action.

I forgot to update it here. I checked this myself and found out that the source position is correctly detected when the static analysis is executed by SonarQube itself.

New goal next week - resolve this issue. Work already started at #900. 5 test cases are failing. It should not be hard to resolve them unless it breaks one...

@monperrus Using the maven mode requires passing `--resolve-classpath-from` and the client has to give it the path to a valid maven project. I think we should not make it the...

More context: https://github.com/SpoonLabs/sorald/issues/598#issuecomment-1008903095.

https://github.com/INRIA/spoon/pull/4320 will fix imports of classes from `java.util`. I have figured out why imports like `import com.basho.riak.client.api.commands.kv.FetchValue.Builder;` are present despite the presence fo this [import statement](https://github.com/brianfrankcooper/YCSB/blob/0a43104985bb919cd4ffcc9e1c284e4a564d81cc/riak/src/main/java/site/ycsb/db/riak/RiakKVClient.java#L40). Spoon is unable to...

@khaes-kth do you remember if running in MAVEN mode resolved this?

Hi all, Good news! I just ran our test suites with sonar-java `v7.11.0.29148` and all our tests passed except 3 of them. I investigated the latter and none of them...

The conversation is continued in https://github.com/SpoonLabs/sorald/issues/659. Closing.