I have a multi-module Gradle java-based project. I have a Sonar server configured with a host of rules. I have tried to integrate Sonar rules into the project in the three following ways, none of which yield a solution where the IDE issues flagged match the Sonar server's flagged issues.
Has anyone integrated Sonar Findbugs, PMD and Checkstyle rules with Intellij on a multi-module Gradle-built java project?
I've tried these steps:
Attempt #1
Sonar has put out an Intellij plugin (https://github.com/SonarSource/sonar-intellij). I attempted to install and configure it with my Sonar server. The plugin was able to hit the Sonar server to pull down profiles, but it was not able to integrate with our gradle project. Right now only multi-module Maven projects appear to be supported by this plugin.
Attempt #2
There is a community developed Sonar Intellij plugin (https://github.com/sonar-intellij-plugin/sonar-intellij-plugin). I stepped through documentation install steps and did troubleshooting to integrate the plugin with individual modules and the top level project. Neither works. When i select 'sync with sonar' I am not able to see the sonar profile when I edit the profiles in 'Analyze code' within the Intellij IDE.
Attempt #3
I found another Intellij plugin called QAPlug (http://plugins.jetbrains.com/plugin/4594) and followed some instructions to export Sonar Findbugs, PMD & Checkstyle rules so that I could import them into this QAPlug and analyze the code using the same rules as the Sonar server. I followed these instructions (http://qaplug.com/about/tutorials/) and got errors when trying to import the FindBugs config I had exported from Sonar. I did some Regex and reformatted the Findbugs component of the export from Sonar to convert it to the format that is importable to the QAPlug plugin in Intellij. I was able to import this ruleset, but got different results from those in Sonar itself. I got the same effect when I followed the advice from post: Sonar, QAPlug, IntelliJ Integration - Multiple profiles?
I contacted Intellj directly and their response to me was to use the community developed plugin (Attempt #2 above).
Given that answer and the lack of additional feedback here, the answer appears to be sonar integration with Intellij 13 is not supported for multi-module gradle java projects by the currently available plugins.
Related
This looks like common issue. I have tried most of solutions on the web. Unfortunately non of them worked for me. I am using IntelliJ 2019.3 Ultimate edition
Cucumber-Java (bundle) and Gherkin (bundle) plugins already there.
Solutions tried:
Check SubType IntelliJ plugin
File types
Plugin
This is Maven project, I got following doubts
Should I add info.cukes to project POM despite of having plugin in the IDE. Even one of my Gradle project also facing the same issue.
Is this mandatory, if so why. Because I can't find cucumber.api.cli.main to set in the Main Class
Answer
You can set the glue location globally by opening "Edit Configurations
-> Defaults -> Cucumber Java -> Glue" and add the package names.
What does this mean
Answer
My project did not have the steps marked as test source root
Can anyone shed some light here please.
This question already has answers here:
Kotlin not working with Eclipse Workspace Resolution
(2 answers)
Closed 3 years ago.
UPDATE
I edited the question after doing additional troubleshooting and realizing that the issue is specific to Kotlin and not a general problem with Eclipse.
ORIGINAL QUESTION
In an earlier question, I found that I need to set the Disable Workspace Resolution setting in order to successfully deploy applications to Tomcat within Eclipse, when the application has references to co-developed dependencies (i.e. dependencies which I am also primarily developing along with the main application). The Disable Workspace Resolution setting has many inconveniences, not the least of which is a need to run mvn install any time the code in a dependency project is modified.
My question now is:
What do I need to configure, either in Eclipse, Maven, or Tomcat, in order to start using Enable Workspace Resolution successfully with Kotlin?
I have reviewed essentially all of the SO questions on the topic, unfortunately none of them specifically address Eclipse with Kotlin:
Eclipse maven-enabled web app references workspace projects, but those are not deployed when running Tomcat server
How to get Maven plugin to use Eclipse workspace resolution?
Maven workspace resolution horked
maven-assembly-plugin and eclipse Workspace resolution
How make Eclipse uses maven projects even if Workspace resolution is not working?
maven eclipse workspace resolution
Maven workspace resolution missing jars for local Tomcat testing
Maven project and Eclipse workspace
M2E Eclipse Maven Workspace resolution and CDI
Eclipse Maven Workspace Resolution not seeing Generated Classes
Using Tomcat within Eclipse for a Maven project
Deploy Maven Project using Eclipse and Tomcat
maven + eclipse + tomcat : class not found exception
How to run a Maven Project In Tomcat From Eclipse
Deployment to tomcat from eclipse via M2eclipse and Maven
Go through following steps,
Enable Workspace Resolution for your project.
Right-click the project, then Maven > Enable Workspace Resolution.
Finally, if your project no longer resolved,
Right-click the project, then Maven > Update Project
This should resolve your problem. If after this, your dependencies are still referenced from the file system, test the groupId, artifactId and particularly model of each dependency again.
And check if you don't have any errors in your project
try to run Maven install.
We upgraded one of our Eclipse 3.x plugins to work with Java 9.
But when we generated the plugin update site content, and used Eclipse Update functionality to install the new version of the plugin, we encountered the following error in Eclipse Oxygen.
Removing part descriptor with the 'pluginxxx.bla.bla' id and the 'bla bla' description. Points to the invalid 'bundleclass://org.eclipse.ui.workbench/org.eclipse.ui.internal.e4.compatibility.CompatibilityView' class.
This error also appears due to some of the bundled plugins of Eclipse Oxygen itself.
After a hard week we had to
Uninstall our plugin
Remove the older versions of the plugin from the Eclipse/plugins folder
Export the plugin as a deployable plugin under the eclipse plugins directory. (Eclipse/plugins/blabla.jar)
Restart Eclipse and it worked.
Right click the eclipse plugin project and Run as "Eclipse Application" works fine, but installing the plugin from an "Update Site" causes the plugin to fail loading.
We could not find a solution yet, but it certainly effects our delivery of the plugin. The plugin is used by almost 500 CS students on their personal computers, and 200 lab computers. So the update should be installed using regular Eclipse Update functionality, not by copying the jar into the plugins directory.
Was there a better way to fix this, or something quicker we could've tried (in case this happens again)?
Update (7 days into the problem)
We have a workaround:
Export the feature project with the following settings in the Export Wizard
Destination/ Directory: Folder of your Plugin Update Site project
Options/ Package as individual JAR archieves (selected)
Options/ Generate p2 repository (selected)
Options/ Allow for binary cycles in target platform (selected)
Options/ Use class files compiled in the workspace (essentially selected)
Install (or update) the plugin from the local (or remote) plugin update site, and the CompatibilityView problem is solved.
In order to have the category listing displayed correctly during install/update new software operations, we added a category.xml file (File/New/Other/Plugin-in Development/Category Definition) in the update site project, defined the categories, and added the feature (versioned as "qualifier").
This is certainly not the way it should be, and we just hope it will be solved in the future Eclipse releases.
By the way current Eclipse Photon integration version has the same problem unfortunately.
The organization with whom I'm associated have been using IDE formatter and a similar checkstyle thing in the IDE. The file I have come up with is what a checkstyle plugin supported one, no further detail I have about it.
Kindly Assist Me as I want that file written/generated by eclipse-cs plugin configuration editor to work in SonarQube. The xml file is already in working order in Eclipse IDE but I want my Checkstyle-configuration to work in SonarQube now.
Note: I have already installed checkstyle plugin 2.4 in my SonarQube 5.4
What you need is the Eclipse Plugin SonarLint. Available in the Eclipse Marketplace or on their Website. Once you connect you Plugin with your SonarQube Server it will always trigger a check when you save your file.
I get the following error when I try to install FindBugs plugin in Netbeans. Can anyone help me how to resolve -
The plugin org.apache.commons.lang is requested in version 2.4.0.
The following plugin is affected: FindBugs
Some plugins require plugin Settings API to be installed.
The plugin Settings API is requested in version >= 1.33.1 but only 1.31.1 was found. The following plugin is affected: FindBugs
Some plugins require plugin UI Utilities API to be installed.
The plugin UI Utilities API is requested in version >= 7.39.1 but only 7.31.2 was found.
The following plugin is affected: FindBugs
Some plugins not installed to avoid potential installation problems.
As it is answered here, you might be using an old ScanOnDemand plugin, you can add the latest Development Plugins to your Plugins: Plugins > Settings Tab > Add and use the following URL to add a new NB Plugins source:
http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/lastStableBuild/artifact/nbbuild/nbms/updates.xml.gz
I have tried this solvation, added the source above with name 'Plugin Resource' and checked available plugins. There, Findbugs Integration plugin appeared and installed successfully. When i restarted the ide to finish the installation, it generated an error and never started again.
Thus, i have downloaded netbeans 7.3 from this link and replaced with the old one (7.0.1) on my computer. Now Findbugs plugin is availabe in the list of available plugins without any additional configuration and works flawless. I recommend you to upgrade your ide to 7.3 and solve your problem. This will fix the problems that may occure in the future because of the lack of version of your current netbeans ide.
In addition, after updating the ide, you can use the findbugs plugin installing from this source. This plugin provides to use findbugs explicitly from the inspector.