How can I clear analysis result for SonarLint in IntelliJ IDEA

tern...@gmail.com

unread,

Mar 22, 2016, 12:57:35 AM3/22/16

to SonarLint

Hi,

How can I clear analysis result for SonarLint in IntelliJ IDEA?

Thanks

Julien HENRY

unread,

Mar 22, 2016, 3:45:22 AM3/22/16

to tern...@gmail.com, SonarLint

Hi,

2016-03-22 5:57 GMT+01:00 <tern...@gmail.com>:

How can I clear analysis result for SonarLint in IntelliJ IDEA?

By fixing the issues :) More seriously, what do you expect? Ability to hide annotations on the code?

++

Julien

Ilia Ternovich

unread,

Mar 22, 2016, 4:03:10 AM3/22/16

to Julien HENRY, SonarLint

Hi,

We have huge legacy codebase which is not possible to refactor fast ;-)

Yes, we would like to hide annotations in code.

Thanks

Duarte Meneses

unread,

Mar 22, 2016, 4:29:46 AM3/22/16

to Ilia Ternovich, Julien HENRY, SonarLint

For the time being, it's not possible to hide issues.

This feature will probably be implemented later at some point.

--
You received this message because you are subscribed to the Google Groups "SonarLint" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarlint+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarlint/CAPP%2BqtD-Ax8DNf7Un3us7ZXz9m5gzB9dfySfL9y1ncuqYsG3kQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Duarte MENESES | SonarSource

http://sonarsource.com

Ilia Ternovich

unread,

Mar 22, 2016, 4:56:32 AM3/22/16

to Duarte Meneses, Julien HENRY, SonarLint

Hello,

Thank you very much for the fast response. Can you please advise the normal workflow with this plugin then and possible timeframe for this improvement?

As I've mentioned before we've got big legacy codebase. It is not possible to eliminate all issues in all files. On the other the side there are tons of different violations not possible to hide (or filter by level) messing developers view.

I suppose this plugin is usable for new projects / where all developers write very good clean code from scratch. But what should we do (except uninstalling plugin) we inherited codebase?

Thanks

Duarte Meneses

unread,

Mar 22, 2016, 5:16:52 AM3/22/16

to Ilia Ternovich, Julien HENRY, SonarLint

A first step towards that feature is to connect SonarLint to a SonarQube server, which will be possible in the upcoming version 2.0.

It will then make it possible to use the information on the server as a baseline for all developers, to show only newly introduced issues. There is no specific time frame for it at the moment but we want to work on it soon.

Right now, the only advice I can give is to use the Issues View to see what are the most recent issues in the file that is being edited.

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarlint/CAPP%2BqtDOsJTRBoVXZNj%3DE%3DFJ%2BUXMOnD_f7ZZfYGSiRwCmnYQbQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

Julien HENRY

unread,

Mar 22, 2016, 5:39:35 AM3/22/16

to Duarte Meneses, Ilia Ternovich, SonarLint

2016-03-22 10:16 GMT+01:00 Duarte Meneses <duarte....@sonarsource.com>:

A first step towards that feature is to connect SonarLint to a SonarQube server, which will be possible in the upcoming version 2.0.

You will then be able to disable rules that are too verbose for your legacy project.

But since we try to make SonarLint usable even for legacy projects would you mind to share rules that are too annoying for your situation?