Using sonar github plugin, I successfully did for several java base based projects
jenkins -> sonar scan -> github pull request
I need to do the same thing for scala based project (regular scala sonar run is good as well).
However, this plugin (sonar-github) seems to dropping all scala scan results.
Anyone with luck for it? Or it is impossible to do? or I need another plugin?
Thanks
Chris L
There's no official code analyzer for Scala. That's the reason why no issues are detected on Scala code.
Note that it does not relate to the GitHub plugin, which aims to decorate pull requests with the issues raised by code analyzers.
Related
As a feedback from a g8 template that I've made, I've been asked whether it's possible to make it available directly inside intellij.
Is there any way to generate new modules from intellij using a g8 template, maybe through some g8 plugin integration? I've made some attempts unsuccessfully and can't find anything documented.
IntelliJ doesn't currently support giter8 directly. If you would like to see it, please vote on this issue on the IntelliJ Scala YouTrack.
I recently created a libGDX project using vis-runtime version 0.3.4. As due to long build times and requirement for separate runtime-gwt project, GWT support was dropped in 0.3.3 version of vis-runtime.
Maybe TeaVM can be used as web backend, so I am looking for integration of TeaVM with vis-runtime library ?
Take a look of this project (integration of libgdx with teaVM) that uses Maven as build system not Gradle.
Any help would be greatly appreciated.
I created TeaVM backend for libGDX as a prototype. I have no time to maintain it and thought someone from libGDX community becomes interested and picks this project. No one did, so backend is not maintained anymore. You can ask question on libGDX community forums and may be you find someone who is interested in developing my prototype. From my side I can help with fixing bugs in TeaVM and telling how this or that thing works in TeaVM.
Regarding Gradle, there's no official support, but 3rd party plugin is available: https://github.com/edibleday/teavm-gradle-plugin. You can examine source code and see that it's easy to write one. You can even write your own Gradle plugin if you are not satisfied with this one. However, I think that supporting Gradle is a little more complicated task than just wring Gradle plugin. For example, IDE integration is also needed (i.e. IDE must import and setup project from build.gradle).
I have seen that a plugin dedicated to Scala is under development (http://docs.sonarqube.org/display/SONARQUBE45/Scala+Plugin).
Would someone be able to tell me when the development of this plugin will be completed and when it could be available through the SonarQube Update Center ?
I also found an other plugin (https://github.com/RadoBuransky/sonar-scoverage-plugin).
Do you plan to propose it in the SonarQube Update Center ?
Thanks
There is an official SonarSource Scala plugin. The documentation is here:
https://docs.sonarqube.org/latest/analysis/languages/scala/
EDIT 03 Aug 2018
You could use mwz/sonar-scala plugin. I see it is up-to-date.
The page http://docs.sonarqube.org/display/SONARQUBE45/Scala+Plugin is very old and outdated.
There is no any official Scala plugin and probably will not be implemented in the near future.
From mailing list:
Where is the official Sonar Scala plugin? (07/Jul/2015)
Freddy Mallet: there isn't any official SonarQube Scala plugin
Source Code of Scala Plugin? (28/Aug/2015)
Dinesh Bolkensteyn: it has been removed due to the lack of activity. [...] you can find the latest master here: https://github.com/hgomez-sonarsource/sonar-scala
Looks like somebody else stepped up to fill the void. Check out this plugin.
I've spent about a day on Google trying to find an answer to this, but to no avail.
Our instance of JIRA has a customised workflow for our project and we would like to use the NetBeans JIRA module to transition issues to the next step in our workflow ("Testing") when our developers commit a change.
However, the JIRA module in NetBeans does not offer any transitions in either the Commit dialog or the Edit Issue window.
We've tried a vanilla JIRA instance with the default workflow and that works fine, but we want a more detailed workflow for our project.
I can't even find an author or even source for this module.
Any help would be appreciated.
I eventually got around to downloading the entire NetBeans source and picked through the JIRA plugin code.
The workflow IS hard-wired to the standard default JIRA workflow.
However, after consultation with the author of the plug-in, we have come up with a way to make the plug-in compatible with any workflow.
Hopefully an update to the plug-in will be available from the 7.3 beta version of NetBeans.
For the last few years, we've used m2eclipse without issue, however it seems that the "new" version (ie. m2e) has broken backwards compatibility - something that I really hope that I've just misinterpreted.
My problem is this: I'd like to be able to build my existing project with the minimal amount of fuss. I don't have the time to write connectors for the 3 plugins that don't have them - my understanding of 2 of them is quite limited in the first place, and I have no understanding of the Eclipse plugin mechanism - but I'd still like to be able to use Eclipse to build the project.
Can I achieve this without reverting back to the old (working) version m2eclipse?
Am I correct in my understanding that there is no way to upgrade without having a connector for each plugin?
It seems as if my understanding was correct if this blog post is anything to go by:
http://grumpyapache.blogspot.com.au/2011/08/mess-that-is-m2e-connectors.html
M2E can invoke a plugin as part of the automatic build process if, and only if, there is a connector for the plugin, or you specially configure the plugin
... which means that:
You can no longer use your own plugins in the Eclipse automatic builds, unless you create a connector for the plugin, or create a project-specific configuration
The post goes on to list the issues with this approach. These are many of the same issues I have with the approach.
RANT: So there you have it - the m2e approach does suck as much as I feared it did! I was beginning to think it was just me!