Martin Wittlinger

So after some thoughts I believe there are 2 ways to integrate the laughing-train code or qodana in sorald. The fast way is to integrate the current refactorings with their...

I'm currently experimenting with the second option, and kinda works. The current results and automatic fixable bad smells for some projects can be found here https://github.com/MartinWitt/laughing-train/tree/gh-mining. The real benefit from...

So after some more experimenting: ## How to integrate Qodana More or less simple if we assume a docker host is running. Pull the image if it isn't available local...

> What about adding Collection findViolations(Path projectRoot, List rule, List classpath):? Would you PR this? I would add this interface after I created a working example for Qodana in Sorald....

As the GSoC proposal was rejected, this task is now again a hot topic. We should first define a goal for a first rule we have as initial target. The...

This is the million-dollar question. It depends on the research scope, goal and future vision of the project. Are there any actual plans to integrate more analyzers into Sorald? Is...

> To my knowledge, I don't think so there is a repair tool by JetBrains to fix Qodana warnings. The repair tool is more or less IntelliJ. But you are...

I'm currently testing the SPI refactoring inside my fork of the repo. It seems like the first goal to refactor Sorald as a platform for analyzers and repair is to...

So as I'm making progress, let's discuss the SPI idea here. Refactoring to SPI seems essential before we can add Qodana in add non-intrusive way. ## New Interfaces/Types I would...

> Do we load all classes or the one specified? In my head, I was imagining that in future a user will provide the name of the static analyzer through...