在线时间:8:00-16:00
迪恩网络APP
随时随地掌握行业动态
扫描二维码
关注迪恩网络微信公众号
SonarJavaSonarJava is a code analyzer for Java projects. Information about the SonarJava features is available here. Build status (all branches) Features
Useful linksHave question or feedback?To provide feedback (request a feature, report a bug etc.) use the SonarQube Community Forum. Please do not forget to specify the language (Java!), plugin version and SonarQube version. If you have a question on how to use plugin (and the docs don't help you), we also encourage you to use the community forum. ContributingTopic in SonarQube Community ForumTo request a new feature, please create a new thread in SonarQube Community Forum. Even if you plan to implement it yourself and submit it back to the community, please start a new thread first to be sure that we can use it. Pull Request (PR)To submit a contribution, create a pull request for this repository. Please make sure that you follow our code style and all tests are passing (Travis build is created for each PR). Custom RulesIf you have an idea for a rule but you are not sure that everyone needs it you can implement a custom rule available only for you. Note that in order to help you, we highly recommend to first follow the Custom Rules 101 tutorial before diving directly into implementing rules from scratch. TestingTo run tests locally follow these instructions. Build the Project and Run Unit TestsTo build the plugin and run its unit tests, execute this command from the project's root directory: mvn clean install Integration TestsTo run integration tests, you will need to create a properties file like the one shown below, and set the url pointing to its location in an environment variable named # version of SonarQube Serversonar.runtimeVersion=6.7orchestrator.updateCenterUrl=http://update.sonarsource.org/update-center-dev.properties# Location of Maven local repository is not automatically guessed. It can also be set with the env variable MAVEN_LOCAL_REPOSITORY.maven.localRepository=/home/myName/.m2/repository With for instance the export ORCHESTRATOR_CONFIG_URL=file:///home/user/workspace/orchestrator.properties Before running the ITs, be sure your MAVEN_HOME environment variable is set. Plugin TestThe "Plugin Test" is an integration test suite which verifies plugin features such as metric calculation, coverage etc. To launch it: mvn clean install -Pit-plugin Ruling TestThe "Ruling Test" are an integration test suite which launches the analysis of a large code base, saves the issues created by the plugin in report files, and then compares those results to the set of expected issues (stored as JSON files). To run the test, first make sure the submodules are checked out: git submodule init git submodule update Launch ruling test: cd its/rulingmvn clean install -DskipTests=false This test gives you the opportunity to examine the issues created by each rule and make sure they're what you expect. Any implemented rule is highly likely to raise issues on the multiple projects we use as ruling code base.
All the its/ruling/target/actual/ Into the directory with the expected issues: its/ruling/src/test/resources/ For example using the command: cp its/ruling/target/actual/* its/ruling/src/test/resources/ LicenseCopyright 2012-2018 SonarSource. Licensed under the GNU Lesser General Public License, Version 3.0 |
请发表评论