Re: [ERROR] Start pointer [line=813, lineOffset=0] should be before end pointer [line=813, lineOffset=0]

1,094 views
Skip to first unread message
Message has been deleted

Julien HENRY

unread,
Nov 24, 2016, 7:13:22 AM11/24/16
to SonarQube
Hi,

Could you please provide:
  - version of SonarQube
  - version of the SonarQube Java plugin
  - possibly a copy of this file (or a smaller reproducer)

Thanks

Julien

Le jeudi 24 novembre 2016 12:59:38 UTC+1, Hugo Fatela a écrit :
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 25.150 s
[INFO] Finished at: 2016-11-24T11:30:11+00:00
[INFO] Final Memory: 60M/447M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.2:sonar (default-cli) on project audit_project: SonarQube is unable to analyze file : 'xxxxxxxxxxx/AuditController.java': Start pointer [line=813, lineOffset=0] should be before end pointer [line=813, lineOffset=0] -> [Help 1]
The problem can be resumed to a java file we have called AuditController.java that instead of beeing removed by the developer he decided to comment it from top to bottom with "//". Sonar doesn't react very well to all coment file contents (see error above). Removing the file solved the problem, but I think Sonar could deal with this issue better. 

Julien HENRY

unread,
Nov 24, 2016, 7:14:08 AM11/24/16
to SonarQube
I forgot to ask for a full stacktrace (run Maven with -e).
Message has been deleted
Message has been deleted

sunilg...@gmail.com

unread,
Dec 7, 2016, 7:30:50 AM12/7/16
to SonarQube
Does anyone knows the solution for this issue ?

Please help. I am facing same issue.


Regards,
Sunil

Michael Gumowski

unread,
Dec 7, 2016, 10:53:43 AM12/7/16
to sunilg...@gmail.com, SonarQube
Hello Ugo, Sunil,

Thanks for the feedback. It's a bug with the Java Analyzer. This ticket has been created to handle the issue: SONARJAVA-1992

Note that this rule was working with SonarQube 5.6.3 (LTS), but the API of SonarQube 6.X has been strengthened in order to better control the size of ranges which are provided for location of issues. As the Java analyzer is providing an empty range, it now fails the analysis.

As a workaround, you can temporarily disable rule S2309 (empty files). The ticket is currently planned for version 4.4 of the Java Analyzer.

Regards,
Michael

--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/41fb5add-73bc-429a-a5d7-ad542b4a7aa8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--

Michael GUMOWSKI | SonarSource
Software Developer @ Language Team
http://sonarsource.com

simo...@gmail.com

unread,
Mar 14, 2017, 12:57:47 PM3/14/17
to SonarQube, sunilg...@gmail.com
Hi Michael

I have the same issue on C# project, is there an issue with C# Analyzer v 1.20.1.1275 as well? I don't see 2309 rule...
regards
Simon

Michael Gumowski

unread,
Mar 15, 2017, 12:38:05 PM3/15/17
to simo...@gmail.com, SonarQube, sunilg...@gmail.com
Hello Simon,

Please open a new thread and don't bump on this one. Our analyzers have relatively fast increment in versions, and things have probably changed since last December.

When opening the new thread, please also provide the stacktrace you are getting, and the versions of the SonarQube and all the analyzers used during analysis. A sample file reproducing the issue will be greatly appreciated as well.

Regards,
Michael


For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages