Run Analyse on entire project

[Viswanathan S]

Hello,

I have installed SonarLint in 

Version: Mars.1 Release (4.5.1)

Build id: 20150924-1200

how to analyse SonarLint for the entire project? 

I can do for each class level.

[l.tourreau]

Hi

I am afraid to say it is no more possible to do that with SonarLint (although previous SonarQube Eclipse plugin was able to do that).

With SonarLint the analysis is done on the fly at the class level when you open the source file.

Regards

Laurent TOURREAU

[marco.m...@gmail.com]

Hi Laurent,

are you guys planning to re-add such functionality?

It is useful for us to invoke the full analysis on a project and than tackle the issues on phasing approach.

[Fabrice Bellingard]

On Wed, Jun 1, 2016 at 2:57 PM, <marco.m...@gmail.com> wrote:

Hi Laurent,

are you guys planning to re-add such functionality?

It is useful for us to invoke the full analysis on a project and than tackle the issues on phasing approach.

This question has been discussed many times, and our position hasn't changed:

• You want very fast feedback on the code you are working on to make sure you don't inject issues => SonarLint analyses the files as you open them to write or review code
• You want a 360° vision of the quality of your code => SonarQube analyses all the files of your project

For the moment, we want our products to perfectly meet those use cases - and we still have some work to do. Once we reach that point, we'll probably see how to better cover the analysis of change sets. But analysis of a whole project is definitely on SonarQube side for the moment, not on SonarLint side (which doesn't mean that we won't make it possible to show information from SonarQube within SonarLint when you are in connected mode).

 

Il giorno lunedì 30 maggio 2016 14:30:26 UTC+1, l.tourreau ha scritto:

Hi

I am afraid to say it is no more possible to do that with SonarLint (although previous SonarQube Eclipse plugin was able to do that).

With SonarLint the analysis is done on the fly at the class level when you open the source file.

Regards

Laurent TOURREAU

Le lundi 30 mai 2016 12:21:15 UTC+2, Viswanathan S a écrit :

Hello,

I have installed SonarLint in 

Version: Mars.1 Release (4.5.1)

Build id: 20150924-1200

how to analyse SonarLint for the entire project? 

I can do for each class level.

--
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/7a54d11d-7f3e-4715-a7b0-8eee5b893e1b%40googlegroups.com.

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

[marco.m...@gmail.com]

Make sense what you are saying.

Thanks for quick turnaround.

Marco

[Viswanathan S]

Thanks for information.

[lof...@gmail.com]

On Wednesday, June 1, 2016 at 3:42:36 PM UTC+2, Fabrice Bellingard wrote:

This question has been discussed many times, and our position hasn't changed:

• You want very fast feedback on the code you are working on to make sure you don't inject issues => SonarLint analyses the files as you open them to write or review code
• You want a 360° vision of the quality of your code => SonarQube analyses all the files of your project

For the moment, we want our products to perfectly meet those use cases - and we still have some work to do. Once we reach that point, we'll probably see how to better cover the analysis of change sets. But analysis of a whole project is definitely on SonarQube side for the moment, not on SonarLint side (which doesn't mean that we won't make it possible to show information from SonarQube within SonarLint when you are in connected mode).

I think many developers are confused since the now deprecated SonarQube Eclipse plugin was able to show SonarQube issues.
When "connected mode" was introduced, again I got the impression this feature had been implemented.

In my workflow, SonarQube is run nightly. It would be useful if I could see detected issues in Eclipse to fix them without switching to the web interface all the time. This is the main feature I am expecting from the Eclipse plugin. Judging from this mailing list, I am not alone ;)

Maybe you could clarify this "missing feature" in the documentation to avoid confusion?

Regards,
Erik

[Fabrice Bellingard]

Hi Erik,

yes, and I think you are referring to this ticket https://jira.sonarsource.com/browse/SLE-54

Best regards,

Fabrice BELLINGARD | SonarSource SonarQube & SonarLint Product Manager http://sonarsource.com

--

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/c5dd3f79-b773-4044-9d61-56f306502944%40googlegroups.com.

[Marco Monti]

Yeah also this solution would work.

Thanks Fabrice

Marco

[emekaa...@gmail.com]

I think I understand the objective above of quick feedback as a developer is creating new code, or updating some existing one - and it will work well in such scenarios. But what of a scenario where there is already existing code that contains issues (because sonar had not been introduced initially) - in order to determine what issues are in such a project and to fix - the developer has to open each and every file in that project?  I think it is very useful for a developer to be able to analyze a project - see all existing issues and fix.

[markus.m...@gmail.com]

I totally agree with the previous notes. Getting a rough overview of the projects issues at one glance would be very helpful - without going through all the files.
There is already a JIRA issue: https://jira.sonarsource.com/browse/SLE-54 which should solve that !?