sorry, I should have explained this better.
We have two versions of Sonargraph, "Explorer" (reduced feature set, https://www.hello2morrow.com/products/sonargraph/explorer )
and "Architect" (full feature set, https://www.hello2morrow.com/products/sonargraph/architect9 ).
The download is the same, the activation code controls which features are available. This applies to the RCP as well as the headless SonargraphBuild.
The activation code that I provided in the last email, is for "Explorer".
Some analyzers won't run, for example you don't get "Architecture Violations" displayed in the SonarQube Sonargraph widgets with that license.
To see the full functionality, use this one: 4B80-991F-4712-B152
It's valid until the end of the month.
If you use Maven or Gradle, you don't have to download or install anything, our Maven/Gradle plugin downloads the latest version of SonargraphBuild automatically.
This is described in more detail here: http://eclipse.hello2morrow.com/doc/build/content/integrating_with_maven.html#example_pom
The Git repo contains a small example multi-module Maven project that should make the testing very easy: https://github.com/sonargraph/sonar-sonargraph-integration/tree/master/src/test/AlarmClockMain
Hope that helps!
Cheers,
Ingmar
I will do my best. :-)
I have added a short "Getting Started" section to the Readme.md on GitHub, which is basically a condensed list of points also described in the online documentation.
https://github.com/sonargraph/sonar-sonargraph-integration
If you are using Maven, edit the pom.xml and add the activation code there.
An example is given here: http://eclipse.hello2morrow.com/doc/build/content/integrating_with_maven.html#example_pom
The pom.xml of the example in the GitHub repo contained an installation path that's most definitely invalid on your machine.
You can either pull the latest file from the repo or just remove that configuration parameter from the pom.
If you would rather configure the parameters as command-line arguments, use the following format:
mvn clean package sonargraph:create-report -Dsonargraph.activationCode=<your code> -Dsonargraph.prepareForSonarQube=true sonar:sonar
All available parameters listed here can be specified like this: http://eclipse.hello2morrow.com/doc/build/content/integrating_with_maven.html#d5e417
Frequent cause of errors:
· The Sonargraph maven repository must be configured either in the project's pom.xml or the global Maven settings.xml.
· The parameter prepareForSonarQube must be set to true for the integration with SonarQube.
· The Sonargraph Integration plugin's rules must be activated in the project's quality profile in SonarQube.
If you still don't see metric values of Sonargraph in the plugin's widgets, please send me the console log of the analysis.
Either SonargraphBuild or the Sonargraph plugin should provide status info of any error that happened.
Thanks for your patience,
Ingmar
hello2morrow GmbH, Unsöldstraße 2, 80538 München, Germany. Tel: +49-89- 25557-5708
Handelsregister-Nr. HRB 194643 beim Amtsgericht München, Ust.-IdNr. DE 814332144
Geschäftsführer: Alexander v. Zitzewitz
mvn clean package sonargraph:create-report
The error message on the console provides the hint:
"[ERROR] Unknown lifecycle phase "create-report". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>."
Up to now, we did not see the need to tie the plugin's execution to a specific lifecycle phase.
Mit freundlichen Grüßen / Best regards,
Ingmar Kellner
hello2morrow GmbH, Unsöldstraße 2, 80538 München, Germany. Tel: +49-89- 25557-5708
Handelsregister-Nr. HRB 194643 beim Amtsgericht München, Ust.-IdNr. DE 814332144
Geschäftsführer: Alexander v. Zitzewitz
did you by any chance just copy+paste the whole example Maven configuration from the online documentation?
A "crm-domain-example.sonargraph" directory does not exist in the sonar-sonargraph-integration project, so I am not surprised about the error message.
All you need to do is to take a look at the following pom.xml of the example project and move the activationCode element from the commented section to the non-commented section (and obviously set the correct value):
Since this is the parent pom for that little example project, navigate in your shell into the folder src/test/AlarmClockMain execute the command-line there.
did you by any chance just copy+paste the whole example Maven configuration from the online documentation?
A "crm-domain-example.sonargraph" directory does not exist in the sonar-sonargraph-integration project, so I am not surprised about the error message.
All you need to do is to take a look at the following pom.xml of the example project and move the activationCode element from the commented section to the non-commented section (and obviously set the correct value):
Since this is the parent pom for that little example project, navigate in your shell into the folder src/test/AlarmClockMain execute the command-line there.
" The pom.xml of the example in the GitHub repo contained an installation path that's most definitely invalid on your machine.
You can either pull the latest file from the repo or just remove that configuration parameter from the pom."
Btw, information about all parameters is available on our searchable online user manual (http://eclipse.hello2morrow.com/doc/build/content/ ) .
Because you requested me to be very explicit ("talk to me like I am 8"), below is a screenshot of what it looks like if you click on the first search result for "installationDirectory maven".
Once you fixed that, it should run through. If not, I can offer to organize a short screensharing session, which might be less frustrating and a lot quicker.
If you don't mind, I would like to follow up on those two issues:
1. You say, you remembered what you changed in the pom, but only show an error message. What DID you need to change?
2. "crm-domain-example.sonargraph" was not part of the example pom and I am still wondering, what the root cause of this error message was...
Best regards,
Ingmar
SonargraphBuild searchable online documentation:

Mit freundlichen Grüßen / Best regards,
Ingmar Kellner
hello2morrow GmbH, Unsöldstraße 2, 80538 München, Germany. Tel: +49-89- 25557-5708
Handelsregister-Nr. HRB 194643 beim Amtsgericht München, Ust.-IdNr. DE 814332144
Geschäftsführer: Alexander v. Zitzewitz
Mit freundlichen Grüßen / Best regards,
Ingmar Kellner
hello2morrow GmbH, Unsöldstraße 2, 80538 München, Germany. Tel: +49-89- 25557-5708
Handelsregister-Nr. HRB 194643 beim Amtsgericht München, Ust.-IdNr. DE 814332144
Geschäftsführer: Alexander v. Zitzewitz
Von: G. Ann Campbell [mailto:ann.ca...@sonarsource.com]
Gesendet: Dienstag, 19. Juli 2016 21:38
An: Ingmar Kellner <i.ke...@hello2morrow.com>
Cc: SonarQube <sona...@googlegroups.com>
Betreff: Re: [VOTE] [NEW RELEASE]: SonarQube Sonargraph 8 Integration Plugin 1.1.2
Hi,
believe it or not, we are getting closer... :-)
As I wrote on Monday:
" The pom.xml of the example in the GitHub repo contained an installation path that's most definitely invalid on your machine.
You can either pull the latest file from the repo or just remove that configuration parameter from the pom."Btw, information about all parameters is available on our searchable online user manual (http://eclipse.hello2morrow.com/doc/build/content/ ) .
Because you requested me to be very explicit ("talk to me like I am 8"), below is a screenshot of what it looks like if you click on the first search result for "installationDirectory maven".
Once you fixed that, it should run through. If not, I can offer to organize a short screensharing session, which might be less frustrating and a lot quicker.
If you don't mind, I would like to follow up on those two issues:
1. You say, you remembered what you changed in the pom, but only show an error message. What DID you need to change?
great!!!
You remember correctly. It would be great to have it as a separate Update Center entry and treat this as a new plugin.
Reason is, that some of our customers are going to migrate over time from Sonargraph 7 -> Sonargraph 8.
They are entirely different products that's why I also took the chance to do a complete rewrite of the plugin.
Rule keys, etc. are also different, and I tested that both plugins can be used in parallel in the same SonarQube instance.
I don't envision a lot of updates to the Sonargraph 7 plugin in the future, but a bug fix here and there (or refactorings due to a changed SQ API) might be needed.
I don't want to split hairs, but we use the term "goal" in our docs, not "target". What you are referring to is "prefix:goal" combination, like "sonar:sonar" or "sonargraph:create-report".
http://stackoverflow.com/questions/2736373/how-to-rename-goals-in-maven gives some details.
Nevertheless, I accept that feedback and I will move the examples for command-line execution to a more prominent position in our docs.
Thanks again for your patience!
Best regards,
Ingmar
hello2morrow GmbH, Unsöldstraße 2, 80538 München, Germany. Tel: +49-89- 25557-5708
Handelsregister-Nr. HRB 194643 beim Amtsgericht München, Ust.-IdNr. DE 814332144
Geschäftsführer: Alexander v. Zitzewitz
Von: G. Ann Campbell [mailto:ann.ca...@sonarsource.com]
Gesendet: Mittwoch, 20. Juli 2016 17:17
An: Ingmar Kellner <i.ke...@hello2morrow.com>
Cc: SonarQube <sona...@googlegroups.com>
Betreff: Re: [VOTE] [NEW RELEASE]: SonarQube Sonargraph 8 Integration Plugin 1.1.2
Hi Ingmar,
yes, exactly because of the limitations you mention and because it is not a continuation of the Sonargraph 7 plugin, I prefer to have a separate UC entry and treat this as a separate independent plugin.
Some of our customers might want to stay with Sonargraph 7 for longer and still be able to use the latest SonarQube.
It would only be for a limited time. I hope that we convinced everybody within a year to move to Sonargraph 8.
If you insist to have only a single "Sonargraph" entry in the UC, well, then I would say that the Sonargraph 7 plugin should be removed and the Sonargraph 8 plugin added.
We will then host the Sonargraph 7 plugin on our own web site.
Mit freundlichen Grüßen / Best regards,
Ingmar Kellner
hello2morrow GmbH, Unsöldstraße 2, 80538 München, Germany. Tel: +49-89- 25557-5708
Sorry about that. Somehow I ended up in the wrong repository.I'm sorry also that this has been so painful.This looks good to me. Let me know when the feedback period is over & this is released.
On Wed, Jul 20, 2016 at 2:25 PM, Ingmar Kellner <i.ke...@hello2morrow.com> wrote:
I had a look at both plugins' pom.xml.
The plugin key is definitely different and the new one follows the guidelines. I am open for suggestions for a better plugin name.
Sonargraph 7:
<plugin>
<groupId>org.sonarsource.sonar-packaging-maven-plugin</groupId>
<artifactId>sonar-packaging-maven-plugin</artifactId>
<version>1.15</version>
<extensions>true</extensions>
<configuration>
<pluginKey>Sonargraph</pluginKey>
<pluginName>Sonargraph</pluginName>
<pluginClass>${sonar.plugin.class}</pluginClass>
</configuration>
</plugin>
<plugin>
Sonargraph 8:
<plugin>
<groupId>org.sonarsource.sonar-packaging-maven-plugin</groupId>
<artifactId>sonar-packaging-maven-plugin</artifactId>
<version>1.15</version>
<extensions>true</extensions>
<configuration>
<pluginName>Sonargraph Integration</pluginName>
<pluginKey>sonargraphintegration</pluginKey>
<pluginClass>${sonar.plugin.class}</pluginClass>
</configuration>
</plugin>
--
You received this message because you are subscribed to a topic in the Google Groups "SonarQube" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sonarqube/m3O6BW0Izvg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/036001d1e711%24c50f2760%244f2d7620%24%40hello2morrow.com.
For more options, visit https://groups.google.com/d/optout.