Eclipse Sonar analyse crashes

[ernesto....@gmail.com]

Did you introduce a new bug with SonarQube 5.1.1?

When I run Sonar analysis in Eclipse 4.4.2 raises an error:

Retrieve remote issues of project sanity-core...
Start SonarQube analysis on sanity-core...
INFO: SonarQube Server 5.1.1
17:02:43.213 INFO  - Preview mode
17:02:43.280 INFO  - Load global repositories
17:02:43.688 INFO  - Load global repositories (done) | time=409ms
17:02:43.690 INFO  - Server id: 20150605162939
17:02:43.692 INFO  - User cache: C:\Users\markovic\.sonar\cache
17:02:43.697 INFO  - Install plugins
17:02:43.838 INFO  - Include plugins:
17:02:43.838 INFO  - Exclude plugins: devcockpit, buildstability, pdfreport, report, buildbreaker, views, jira
17:02:44.352 INFO  - Load project repositories
17:02:44.911 INFO  - Load project repositories (done) | time=559ms
17:02:44.911 INFO  - Load project settings
17:02:45.145 INFO  - Apply project exclusions
17:02:45.209 INFO  - -------------  Scan sanity-core
17:02:45.213 INFO  - Load module settings
17:02:45.393 INFO  - Base dir: C:\dev\ws\tools\sanity\sanity\sanity-core
17:02:45.393 INFO  - Working dir: C:\dev\ws\tools\sanity\.metadata\.plugins\org.eclipse.core.resources\.projects\sanity-core\org.sonar.ide.eclipse.core
17:02:45.395 INFO  - Source paths: src/main/java
17:02:45.396 INFO  - Test paths: src/test/java
17:02:45.396 INFO  - Binary dirs: target/classes
17:02:45.397 INFO  - Source encoding: UTF-8, default locale: en_US
17:02:45.397 INFO  - Index files
17:02:45.482 INFO  - 55 files indexed
17:02:45.486 INFO  - Quality profile for java: Sanity
17:02:45.611 INFO  - Sensor JavaSquidSensor
17:02:46.150 WARN  - sonar.binaries and sonar.libraries are deprecated since version 2.5 of sonar-java-plugin, please use sonar.java.binaries and sonar.java.libraries instead
17:02:46.158 INFO  - Java Main Files AST scan...
17:02:46.161 INFO  - 55 source files to be analyzed
17:02:50.771 INFO  - Java Main Files AST scan done: 4613 ms
17:02:50.771 INFO  - 55/55 source files analyzed
17:02:50.775 INFO  - Java bytecode scan...
17:02:50.905 INFO  - Java bytecode scan done: 130 ms
17:02:50.906 INFO  - Java Test Files AST scan...
17:02:50.906 INFO  - 0 source files to be analyzed
17:02:50.907 INFO  - Java Test Files AST scan done: 1 ms
17:02:50.909 INFO  - Package design analysis...
17:02:50.912 INFO  - 0/0 source files analyzed
17:02:50.951 INFO  - Package design analysis done: 42 ms
17:02:50.971 INFO  - Sensor JavaSquidSensor (done) | time=5360ms
17:02:50.971 INFO  - Sensor Lines Sensor
17:02:50.979 INFO  - Sensor Lines Sensor (done) | time=8ms
17:02:50.979 INFO  - Sensor PmdSensor
17:02:50.980 INFO  - Execute PMD 5.3.1...
17:02:50.995 INFO  - Java version: 1.8
17:02:51.019 INFO  - PMD configuration: C:\dev\ws\tools\sanity\.metadata\.plugins\org.eclipse.core.resources\.projects\sanity-core\org.sonar.ide.eclipse.core\pmd.xml
17:02:53.565 INFO  - Execute PMD 5.3.1 done: 2585 ms
17:02:53.575 INFO  - Sensor PmdSensor (done) | time=2596ms
17:02:53.575 INFO  - Sensor org.sonar.plugins.findbugs.FindbugsSensor@70f43b45
17:02:53.579 INFO  - Execute Findbugs 3.0.1...
17:02:54.733 INFO  - Found findbugs plugin: C:\dev\ws\tools\sanity\.metadata\.plugins\org.eclipse.core.resources\.projects\sanity-core\org.sonar.ide.eclipse.core\findbugs\fb-contrib.jar
17:02:54.772 INFO  - Found findbugs plugin: C:\dev\ws\tools\sanity\.metadata\.plugins\org.eclipse.core.resources\.projects\sanity-core\org.sonar.ide.eclipse.core\findbugs\findsecbugs-plugin.jar
17:02:54.779 INFO  - Findbugs output report: C:\dev\ws\tools\sanity\.metadata\.plugins\org.eclipse.core.resources\.projects\sanity-core\org.sonar.ide.eclipse.core\findbugs-result.xml
17:03:02.380 INFO  - Execute Findbugs 3.0.1 done: 8801 ms
17:03:02.396 INFO  - Sensor org.sonar.plugins.findbugs.FindbugsSensor@70f43b45 (done) | time=8821ms
17:03:02.396 INFO  - Sensor SurefireSensor
17:03:02.397 INFO  - parsing C:\dev\ws\tools\sanity\sanity\sanity-core\target\surefire-reports
17:03:02.397 WARN  - Reports path not found: C:\dev\ws\tools\sanity\sanity\sanity-core\target\surefire-reports
17:03:02.397 INFO  - Sensor SurefireSensor (done) | time=1ms
17:03:02.397 INFO  - Sensor CheckstyleSensor
17:03:02.398 INFO  - Execute Checkstyle ${checkstyle.version}...
17:03:02.410 INFO  - Checkstyle configuration: C:\dev\ws\tools\sanity\.metadata\.plugins\org.eclipse.core.resources\.projects\sanity-core\org.sonar.ide.eclipse.core\checkstyle.xml
17:03:03.898 INFO  - Execute Checkstyle ${checkstyle.version} done: 1500 ms
17:03:03.898 INFO  - Sensor CheckstyleSensor (done) | time=1501ms
17:03:03.898 INFO  - Load server issues
17:03:05.495 INFO  - Export issues to C:\dev\ws\tools\sanity\.metadata\.plugins\org.eclipse.core.resources\.projects\sanity-core\org.sonar.ide.eclipse.core\sonar-report.json
17:03:05.714 INFO  - ANALYSIS SUCCESSFUL
Exception in thread "main" org.sonar.runner.impl.RunnerException: Unable to execute Sonar
    at org.sonar.runner.impl.BatchLauncher$1.delegateExecution(BatchLauncher.java:91)
    at org.sonar.runner.impl.BatchLauncher$1.run(BatchLauncher.java:75)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.sonar.runner.impl.BatchLauncher.doExecute(BatchLauncher.java:69)
    at org.sonar.runner.impl.BatchLauncher.execute(BatchLauncher.java:50)
    at org.sonar.runner.impl.BatchLauncherMain.execute(BatchLauncherMain.java:41)
    at org.sonar.runner.impl.BatchLauncherMain.main(BatchLauncherMain.java:59)
Caused by: org.picocontainer.injectors.AbstractInjector$UnsatisfiableDependenciesException: org.sonar.core.notification.DefaultNotificationManager has unsatisfied dependency 'class org.sonar.core.properties.PropertiesDao' for constructor 'public org.sonar.core.notification.DefaultNotificationManager(org.sonar.core.notification.db.NotificationQueueDao,org.sonar.core.properties.PropertiesDao)' from org.picocontainer.DefaultPicoContainer@64b0598:214<[Immutable]:org.picocontainer.DefaultPicoContainer@865dd6:17<[Immutable]:org.picocontainer.DefaultPicoContainer@35badbfc:43<|
    at org.picocontainer.injectors.ConstructorInjector.getGreediestSatisfiableConstructor(ConstructorInjector.java:191)
    at org.picocontainer.injectors.ConstructorInjector.getGreediestSatisfiableConstructor(ConstructorInjector.java:110)
    at org.picocontainer.injectors.ConstructorInjector.access$100(ConstructorInjector.java:51)
    at org.picocontainer.injectors.ConstructorInjector$1.run(ConstructorInjector.java:331)
    at org.picocontainer.injectors.AbstractInjector$ThreadLocalCyclicDependencyGuard.observe(AbstractInjector.java:270)
    at org.picocontainer.injectors.ConstructorInjector.getComponentInstance(ConstructorInjector.java:364)
    at org.picocontainer.injectors.AbstractInjectionFactory$LifecycleAdapter.getComponentInstance(AbstractInjectionFactory.java:56)
    at org.picocontainer.behaviors.AbstractBehavior.getComponentInstance(AbstractBehavior.java:64)
    at org.picocontainer.behaviors.Stored.getComponentInstance(Stored.java:91)
    at org.picocontainer.DefaultPicoContainer.getInstance(DefaultPicoContainer.java:698)
    at org.picocontainer.DefaultPicoContainer.getComponent(DefaultPicoContainer.java:646)
    at org.picocontainer.DefaultPicoContainer.getComponent(DefaultPicoContainer.java:620)
    at org.picocontainer.containers.ImmutablePicoContainer.getComponent(ImmutablePicoContainer.java:40)
    at org.picocontainer.DefaultPicoContainer.getInstance(DefaultPicoContainer.java:717)
    at org.picocontainer.DefaultPicoContainer.getComponent(DefaultPicoContainer.java:646)
    at org.picocontainer.DefaultPicoContainer.getComponent(DefaultPicoContainer.java:631)
    at org.picocontainer.parameters.BasicComponentParameter$1.resolveInstance(BasicComponentParameter.java:118)
    at org.picocontainer.parameters.ComponentParameter$1.resolveInstance(ComponentParameter.java:136)
    at org.picocontainer.injectors.SingleMemberInjector.getParameter(SingleMemberInjector.java:78)
    at org.picocontainer.injectors.ConstructorInjector$CtorAndAdapters.getParameterArguments(ConstructorInjector.java:309)
    at org.picocontainer.injectors.ConstructorInjector$1.run(ConstructorInjector.java:335)
    at org.picocontainer.injectors.AbstractInjector$ThreadLocalCyclicDependencyGuard.observe(AbstractInjector.java:270)
    at org.picocontainer.injectors.ConstructorInjector.getComponentInstance(ConstructorInjector.java:364)
    at org.picocontainer.injectors.AbstractInjectionFactory$LifecycleAdapter.getComponentInstance(AbstractInjectionFactory.java:56)
    at org.picocontainer.behaviors.AbstractBehavior.getComponentInstance(AbstractBehavior.java:64)
    at org.picocontainer.behaviors.Stored.getComponentInstance(Stored.java:91)
    at org.picocontainer.DefaultPicoContainer.getLocalInstance(DefaultPicoContainer.java:605)
    at org.picocontainer.DefaultPicoContainer.getComponents(DefaultPicoContainer.java:586)
    at org.sonar.api.platform.ComponentContainer.getComponentsByType(ComponentContainer.java:217)
    at org.sonar.batch.bootstrap.BatchExtensionDictionnary.completeBatchExtensions(BatchExtensionDictionnary.java:119)
    at org.sonar.batch.bootstrap.BatchExtensionDictionnary.getExtensions(BatchExtensionDictionnary.java:113)
    at org.sonar.batch.bootstrap.BatchExtensionDictionnary.getFilteredExtensions(BatchExtensionDictionnary.java:91)
    at org.sonar.batch.bootstrap.BatchExtensionDictionnary.select(BatchExtensionDictionnary.java:68)
    at org.sonar.batch.phases.PostJobsExecutor.execute(PostJobsExecutor.java:49)
    at org.sonar.batch.phases.DatabaseLessPhaseExecutor.execute(DatabaseLessPhaseExecutor.java:103)
    at org.sonar.batch.scan.ModuleScanContainer.doAfterStart(ModuleScanContainer.java:264)
    at org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:92)
    at org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77)
    at org.sonar.batch.scan.ProjectScanContainer.scan(ProjectScanContainer.java:235)
    at org.sonar.batch.scan.ProjectScanContainer.scanRecursively(ProjectScanContainer.java:230)
    at org.sonar.batch.scan.ProjectScanContainer.doAfterStart(ProjectScanContainer.java:220)
    at org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:92)
    at org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77)
    at org.sonar.batch.scan.ScanTask.scan(ScanTask.java:57)
    at org.sonar.batch.scan.ScanTask.execute(ScanTask.java:45)
    at org.sonar.batch.bootstrap.TaskContainer.doAfterStart(TaskContainer.java:135)
    at org.sonar.api.platform.ComponentContainer.startComponents(ComponentContainer.java:92)
    at org.sonar.api.platform.ComponentContainer.execute(ComponentContainer.java:77)
    at org.sonar.batch.bootstrap.GlobalContainer.executeTask(GlobalContainer.java:158)
    at org.sonar.batch.bootstrapper.Batch.executeTask(Batch.java:95)
    at org.sonar.batch.bootstrapper.Batch.execute(Batch.java:67)
    at org.sonar.runner.batch.IsolatedLauncher.execute(IsolatedLauncher.java:45)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.sonar.runner.impl.BatchLauncher$1.delegateExecution(BatchLauncher.java:87)
    ... 6 more

[Fabrice Bellingard]

As explained on the description of this Google group, such question should be posted on Stackoverflow, thanks for your understanding.

Best regards,

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

--
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/216ec5cd-106f-4b98-979e-238cf293ffde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[ernesto....@gmail.com]

Okay, but if would had used just one Forum you could have simply moved the topic into the right folder.

There was not written where bugs have to be posted, I didn't know they are "support questions".

[Fabrice Bellingard]

On Thu, Jun 11, 2015 at 12:55 PM, <ernesto....@gmail.com> wrote:

Okay, but if would had used just one Forum you could have simply moved the topic into the right folder.

There was not written where bugs have to be posted, I didn't know they are "support questions".

You're right, I have improved the message to detail what "support questions" are.

 

--
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/45f6bb0f-0f9d-4884-911a-2d606482cc3d%40googlegroups.com.

[Ajedi32]

FYI, StackOverflow is not affiliated with SonarQube, and is not equipped to deal with certain types of "support questions", such as bug reports. Please see StackOverflow's policy on this at Can I support my product on this site?.

In particular, it should be noted that the OP attempted to re-post this question on StackOverflow and the question got closed as off-topic by the community there.

[Fabrice Bellingard]

On Mon, Jun 15, 2015 at 4:06 PM, Ajedi32 <andre...@gmail.com> wrote:

FYI, StackOverflow is not affiliated with SonarQube, and is not equipped to deal with certain types of "support questions", such as bug reports. Please see StackOverflow's policy on this at Can I support my product on this site?.

If you read carefully this page, you will see that what we're doing is aligned with their suggestions:

• How do I? / I got this error, why ? => support questions => SOF
• I have an idea or request / Why do you? / When will you? => open discussions => SonarQube Google group 

 

In particular, it should be noted that the OP attempted to re-post this question on StackOverflow and the question got closed as off-topic by the community there.

This question was downvoted 11 times and 5 moderators (not affiliated with SonarSource) voted to close it, not because it's off-topic, but because it did not comply with "How to create a Minimal, Complete and Verifiable example". 

You can't expect to have support when you don't take the time to ask a question correctly. 

Best regards,

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

 

On Thursday, June 11, 2015 at 6:23:34 AM UTC-5, Fabrice Bellingard wrote:

On Thu, Jun 11, 2015 at 12:55 PM, <ernesto....@gmail.com> wrote:

Okay, but if would had used just one Forum you could have simply moved the topic into the right folder.

There was not written where bugs have to be posted, I didn't know they are "support questions".

You're right, I have improved the message to detail what "support questions" are.

 

--
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/45f6bb0f-0f9d-4884-911a-2d606482cc3d%40googlegroups.com.

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

--
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/9ec788a1-e812-4cfa-83f6-0ee7fe990126%40googlegroups.com.

[Ajedi32]

Regarding the StackOverflow policy, it seems to me that since the OP mentioned a bug. ("Did you introduce a new bug with SonarQube 5.1.1?") that this falls more under this category from the StackOverflow policy:

• I got this error and I'm sure it's a bug -- file an issue (on your own site)

I'm not at all familiar with SonarSource, so I'm certainly not qualified to judge whether the OP was correct in this assessment or not. I'm pretty sure though that line in the question implying a bug was one of the contributing factors to the question being poorly received. The Stack Overflow can certainly help with debugging, but not if the issue is a bug in a third party product (like SonarQube). In cases like that, only the developers of the product in question can help (which I assume is what this mailing list is for, correct?).

This question was downvoted 11 times and 5 moderators (not affiliated with SonarSource) voted to close it, not because it's off-topic, but because it did not comply with "How to create a Minimal, Complete and Verifiable example". 

 

You can't expect to have support when you don't take the time to ask a question correctly. 

Fair enough. You're certainly free to handle customer support (or not handle it) however you wish. However, I would advise against directing users who are encountering bugs in your product to post on Stack Overflow. Again, the Stack Overflow community can't really do anything about bugs, so questions like that are very likely to get closed rather quickly. Specifically, I would advise you to revise the language on your page at http://www.sonarqube.org/get-support/ which currently says:

Still no luck? You should consider posting a question on Stack Overflow for any user support matter:

 

• installation,
• configuration,
• unexpected behaviour or bug,
• migration issue,
• …etc.

Also, minor nitpicking, but those were ordinary Stack Overflow users who voted to close that question, not site moderators, and a lack of steps necessary to reproduce the problem is indeed one of the "off-topic" close reasons. The close message even says "put on hold as off-topic". The question has been deleted now, but a screenshot is still available here if you want to review it: https://i.stack.imgur.com/Hylyb.png

[Fabrice Bellingard]

For the record: we updated the "Get Support" page to make it clear that we are aligned with Stack Overflow policy detailed at https://stackoverflow.com/help/product-support.

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/6fdd9475-6ec5-4371-9e63-2876d9496287%40googlegroups.com.

[ernesto....@gmail.com]

I posted that question on Stackoverflow, but they rejected it there: http://stackoverflow.com/questions/30778941/eclipse-sonar-analyse-crashes

I am no Sonar customer by the way, I use the free versions.

Is this Catch 22? This gets ridiculous.

Before you spread the single mailing list into two different forum sites it worked so well to report a bug and get it fixed.

Now it seems like noone from the code contributors wants to know anything about bugs.

So I have to ask again: Where can I report that (potential) bug?

[ernesto....@gmail.com]

But on Stackoverflow I did not receive any help on this. The issue was rejected because they say it violates Stackoverflow policy, you are not allowed to use it for that purpose.

Open that link below and read it please.

[Julien HENRY]

Hi Ernesto,

I think you have a plugin that is not compatible with preview mode (trying to send emails in PostJob phase). Could you please give us the list of your installed plugins?

Thanks

Juien