coveralls-maven-plugin - GitLite

KO | EN

gitlite — search

#python #typescript #go #machine-learning #rust #deep-learning #docker #macos #java #kubernetes #awesome-list #security #mcp #open-source

coveralls-maven-plugin

(★ 314)

Maven plugin for submitting Java code coverage reports to Coveralls web service.

파일 탐색기

최종 버전 다운로드 (.zip)

- - pom.xml
- - pom.xml
- pom.xml
- README.md
- bump-version.sh
- functions.sh
- release.sh
.gitignore
.gitmodules
.travis.yml
CHANGELOG.md
etc
LICENSE.MIT
MIGRATION.md
pom.xml
README.md
README_2_x.md

# 설치 가이드

1. 코드 내려받기

git clone https://github.com/trautonen/coveralls-maven-plugin

깃허브에서 프로젝트 코드 전체를 내 컴퓨터로 내려받습니다.

cd coveralls-maven-plugin

방금 내려받은 프로젝트 폴더 안으로 이동합니다.

2. Maven (Java)

보통 추천

사전 준비물

Git GitHub에서 프로젝트 코드를 내려받으려면 필요합니다.
JDK (Java) Java 프로젝트를 빌드/실행하려면 필요합니다.
Maven mvn 명령어를 쓰기 위한 빌드 도구입니다.

mvn cobertura:cobertura coveralls:report

Maven으로 의존성 설치와 빌드를 진행합니다.

- mvn clean cobertura:cobertura coveralls:report

Maven으로 의존성 설치와 빌드를 진행합니다.

mvn clean test jacoco:report coveralls:report

Maven으로 의존성 설치와 빌드를 진행합니다.

- mvn clean test jacoco:report coveralls:report

Maven으로 의존성 설치와 빌드를 진행합니다.

mvn clean test saga:coverage coveralls:report

Maven으로 의존성 설치와 빌드를 진행합니다.

✅ BUILD SUCCESS 메시지가 뜨면 성공입니다. target/ 폴더에 결과물이 생성됩니다.

이 레포의 README에 적힌 실제 명령어를 그대로 가져왔습니다.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

coveralls-maven-plugin
======================

[![No Maintenance Intended](http://unmaintained.tech/badge.svg)](http://unmaintained.tech/)
[![Coverage Status](http://img.shields.io/coveralls/trautonen/coveralls-maven-plugin/master.svg?style=flat-square)](https://coveralls.io/r/trautonen/coveralls-maven-plugin?branch=master)
[![Maven Central](https://maven-badges.herokuapp.com/maven-central/org.eluder.coveralls/coveralls-maven-plugin/badge.svg?style=flat-square)](https://maven-badges.herokuapp.com/maven-central/org.eluder.coveralls/coveralls-maven-plugin/)

Maven plugin for submitting Java code coverage reports to [Coveralls](https://coveralls.io/) web
service.

## !!! Deprecated !!!

This project is deprecated due to lack of time and interest. Please use https://github.com/hazendaz/coveralls-maven-plugin from now on.

### Requirements

* Java 6 up to 3.x and Java 7 for 4.x onwards.
* Maven 3.0.0 or newer.

### Features

* Supports [Cobertura](http://mojo.codehaus.org/cobertura-maven-plugin/),
  [JaCoCo](http://www.eclemma.org/jacoco/trunk/doc/maven.html) and
  [Saga](http://timurstrekalov.github.io/saga/) coverage tools
* Multi-module report aggregation
* Built-in support for [Travis CI](https://travis-ci.org/), [Circle](https://circleci.com/),
  [Codeship](https://www.codeship.io/), [Jenkins](http://jenkins-ci.org/),
  [Bamboo](https://www.atlassian.com/software/bamboo/), [Shippable](https://www.shippable.com/)
  and [Appveyor](http://www.appveyor.com/) continuous integration services
* Fully streaming implementation for fast report generation and small memory footprint
* Provides clean interfaces to allow easy extending to different coverage tools
* Convention over configuration for almost zero configuration usage
* Applies [semantic versioning](http://semver.org/)

### Usage

Set up the Coveralls maven plugin in the build section of the project pom.xml:

```xml
<plugin>
    <groupId>org.eluder.coveralls</groupId>
    <artifactId>coveralls-maven-plugin</artifactId>
    <version>4.3.0</version>
    <configuration>
        <repoToken>yourcoverallsprojectrepositorytoken</repoToken>
    </configuration>
</plugin>
```

#### Configuration

If used as a standalone Maven build or with any continuous integration server other than Travis
CI, the Coveralls repository token must be provided. This can be achieved by setting the
configuration section in the plugin or setting the Maven property `repoToken` to your coveralls
project repository token, using `-DrepoToken=yourcoverallsprojectrepositorytoken` when running the
maven command. **Do not publish your repository token in public GitHub repositories.** If you do,
anyone can submit coverage data without permission.

If you are using Travis CI, CircleCI, Codeship, Jenkins or Bamboo continuous integration services,
no other configuration is required. The plugin's built-in service environment support take care of
the rest. The plugin tries to find report files for any of the supported coverage tools and
finally aggregates the coverage report. Java 8 is currently supported only by JaCoCo.

See [Complete plugin configuration](#complete-plugin-configuration) for all of the available
configuration parameters.

#### Cobertura

Set up the Cobertura Maven plugin with XML report format in the build section of the project
pom.xml:

```xml
<plugin>
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>cobertura-maven-plugin</artifactId>
    <version>2.7</version>
    <configuration>
        <format>xml</format>
        <maxmem>256m</maxmem>
        
        <aggregate>true</aggregate>
    </configuration>
</plugin>
```

Execute Maven to create Cobertura report and submit Coveralls data:

```
mvn cobertura:cobertura coveralls:report
```

For example if you are using Travis CI this means you need to add to your `.travis.yml` the lines:

```
after_success:
  - mvn clean cobertura:cobertura coveralls:report
```

#### JaCoCo

Set up the JaCoCo Maven plugin in the build section of the project pom.xml:

```xml
<plugin>
    <groupId>org.jacoco</groupId>
    <artifactId>jacoco-maven-plugin</artifactId>
    <version>0.7.6.201602180812</version>
    <executions>
        <execution>
            <id>prepare-agent</id>
            <goals>
                <goal>prepare-agent</goal>
            </goals>
        </execution>
    </executions>
</plugin>
```

Execute Maven to create JaCoCo report and submit Coveralls data:

```
mvn clean test jacoco:report coveralls:report
```

Again, if you are using Travis CI this means you need to add to your `.travis.yml` the lines:

```
after_success:
  - mvn clean test jacoco:report coveralls:report
```

#### Saga

Set up the Saga Maven plugin in the build section of the project pom.xml:

```xml
<plugin>
    <groupId>com.github.timurstrekalov</groupId>
    <artifactId>saga-maven-plugin</artifactId>
    <version>1.5.5</version>
    <executions>
        <execution>
            <goals>
                <goal>coverage</goal>
            </goals>
        </execution>
    </executions>
    <configuration>
        <baseDir>http://localhost:${jasmine.serverPort}</baseDir>
        <outputDir>${project.build.directory}/saga-coverage</outputDir>
        <noInstrumentPatterns>
            <pattern>.*/spec/.*</pattern>
            <pattern>.*/classpath/.*</pattern>
            <pattern>.*/webjars/.*</pattern>
        </noInstrumentPatterns>
    </configuration>
</plugin>
```

Note that Saga does not have default report output directory, but the plugin assumes
`${project.build.directory}/saga-coverage`.

Execute Maven to create Saga report and submit Coveralls data:

```
mvn clean test saga:coverage coveralls:report
```

And if you are using Travis CI this means you need to add to your `.travis.yml` the lines:

```
after_success:
  - mvn clean test saga:coverage coveralls:report
```

#### Aggregate multiple reports

Report aggregation is applied by default and the only thing the user must take care of is to run
all the desired coverage tools. You can use JaCoCo in a multi-module project so that all modules
run JaCoCo separately and let the plugin aggregate the report, or you can run Saga and Cobertura
in same project and get coverage report for JavaScript and Java files.

Execute Maven to create Saga and Cobertura report and submit Coveralls data:

```
mvn clean test saga:coverage cobertura:cobertura coveralls:report
```

And if you are using Travis CI this means you need to add to your `.travis.yml` the lines:

```
after_success:
  - mvn clean test saga:coverage cobertura:cobertura coveralls:report
```

### Complete plugin configuration

Configuration can be changed by the configuration section of plugin's definition in POM or with
Java virtual machine system properties using the syntax `-Dparameter=value`. See
[Maven plugin guide](http://maven.apache.org/guides/plugin/guide-java-plugin-development.html#Configuring_Parameters_in_a_Project)
how different types are mapped in the configuration XML. Some of the optional parameters are set
by the built-in service environment setups. Note that if a parameter is explicitly defined, the
service environment will not override it.

| Parameter | Type | Description |
| --------- | ---- | ----------- |
| `jacocoReports` | `List<File>` | List of additional JaCoCo report files. ${project.reporting.outputDirectory}/jacoco/jacoco.xml is used as default for every module. |
| `coberturaReports` | `List<File>` | List of additional Cobertura report files. ${project.reporting.outputDirectory}/cobertura/coverage.xml is used as default for every module. |
| `sagaReports` | `List<File>` | List of additional Saga report files. ${project.build.directory}/saga-coverage/total-coverage.xml is used as default for every module. |
| `relativeReportDirs` | `List<String>` | List of additional relative report directories. Directories relative to ${project.reporting.outputDirectory} and ${project.build.directory} are scanned for reports. |
| `coverallsFile` | `File` | **Default: ${project.build.directory}/coveralls.json**<br>File path to write and submit Coveralls data. |
| `coverallsUrl` | `String` | **Default: https://coveralls.io/api/v1/jobs**<br>Url for the Coveralls API. |
| `sourceDirectories` | `List<File>` | List of additional source directories. The plugin will scan the project's compiled source roots for defaults. |
| `sourceEncoding` | `String` | **Default: ${project.build.sourceEncoding}**<br>Source file encoding. |
| `serviceName` | `String` | CI service name. If not provided the supported service environments are used. |
| `serviceJobId` | `String` | CI service job id. Currently supported only with Travis CI. If this property is set, `repoToken` is not required. If not provided the supported service environments are used. |
| `serviceBuildNumber` | `String` | CI service build number. If not provided the supported service environments are used. |
| `serviceBuildUrl` | `String` | CI service build url. If not provided the supported service environments are used. |
| `serviceEnvironment` | `Properties` | CI service specific environment properties. If not provided the supported service environments are used. |
| `repoToken` | `String` | Coveralls repository token. **Do not publish this parameter unencrypted in public GitHub repositories.** |
| `parallel` | `boolean` | **Default: false**<br> Coveralls API flag: If this is set, the build will not be considered done until a webhook has been sent to https://coveralls.io/webhook?repo_token=… |
| `branch` | `String` | Git branch name. If not provided the supported service environments are used. |
| `pullRequest` | `String` | GitHub pull request identifier. If not provided the supported service environments are used. |
| `timestampFormat` | `String` | **Default: ${maven.build.timestamp}**<br>Build timestamp format. Must be in format supported by SimpleDateFormat. |
| `timestamp` | `String` | **Default: ${timestamp}**<br>Build timestamp. Must be in format defined by 'timestampFormat' if it's available or in default timestamp format yyyy-MM-dd'T'HH:mm:ss'Z'. |
| `dryRun` | `boolean` | **Default: false**<br>Dry run Coveralls report without actually sending it. |
| `failOnServiceError` | `boolean` | **Default: true**<br> Fail build if Coveralls service is not available or submission fails for internal errors. |
| `scanForSources` | `boolean` | **Default: false**<br>Scan subdirectories for source files. |
| `coveralls.basedir` | `File` | **Default: ${project.basedir}**<br>Base directory of the project. |
| `coveralls.skip` | `boolean` | **Default: false**<br>Skip the plugin execution. |

### FAQ

> **Q:** How do I know that my coverage report was submitted successfully to Coveralls?  
> **A:** The plugin will end with BUILD SUCCESS and the log contains the reported job id and
> direct URL to Coveralls.

> **Q:** I get BUILD SUCCESS but why Coveralls shows only question marks in the reports?  
> **A:** The data is most likely reported correctly, but Coveralls might take hours, or even a
> day, to update the actual coverage numbers.

> **Q:** Can I use Java 8 with the plugin?  
> **A:** Yes. The Coveralls plugin works fine with Java 8, but the problem is the coverage tools.
> Currently only tool supporting Java 8 is JaCoCo. You can use JaCoCo in a single module or
> a multi-module project and let the Coveralls plugin handle the report aggregation. This is not
> true aggregation though and does not address cross module coverage calculation (see
> https://github.com/jacoco/jacoco/pull/97)

> **Q:** Build fails with 'javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated'
> exception, what to do?  
> **A:** If the build is run with OpenJDK, you probably hit an issue with the Cryptography Package
> Providers not supporting all Elliptic Curves. The [issue](https://bugs.launchpad.net/ubuntu/+source/openjdk-6/+bug/1006776)
> is described in the Ubuntu issue tracker. A workaround is to disable the PKCS provider from the
> `java.security` options file.
> ```
> sudo sed -i 's/security.provider.9/#security.provider.9/g' $JAVA_HOME/jre/lib/security/java.security
> ```
> In Travis CI the above command can be added to before_install phase. See complete example from
> this project's `.travis.yml`.

> **Q:** How can I use Scala or some other project which sources reside in other folder than
> `src/main/java`?  
> **A:** The plugin uses all compiled source roots available for the project at runtime. If the
> source directories are available, everything is fine. Otherwise additional source directories
> can be applied with `sourceDirectories` configuration parameter that takes a Maven configuration
> style list of source directories.

> **Q:** How can I set the plugin to use multiple source directories?  
> **A:** For multi-module projects, the plugin automatically scans the project hierarchy and adds
> all required source directories. You can also customize the used source directories with
> `sourceDirectories` configuration parameter that takes a Maven configuration style list of
> source directories.

> **Q:** Why source files are not found for generated sources?  
> **A:** Generated source directories under target are not added to the sources list
> automatically. It is often not good practice to test generated code, because the code is not
> managed by the project under test, unless you are testing a source generator. Cobertura and
> JaCoCo both have `<excludes>` configuration directive that provides ignoring of class files. If
> the generated sources still must be tested, all source directories can be explicitly defined
> with `sourceDirectories` configuration parameter.

> **Q:** JaCoCo or Cobertura, which one should i choose?  
> **A:** For multi-module projects, only Cobertura supports report aggregation out of the box. The
> coverage metrics and performance of the two plugins are not much different for a small or medium
> sized project, but there are 2 notable differences with the tools:
> - JaCoCo does not track how many times a single line of code is hit by all the tests together,
> so Coveralls is always reported with 1 as the number of hits if the line is covered. Cobertura
> tracks the number of hits and the number is reported to Coveralls.
> - Cobertura tracks all inner classes separately, so a single source file will contain multiple
> records with same file name in Coveralls if there are any innner classes defined. The
> coveralls-maven-plugin adds classifier from the inner class to distinguish the files, but if
> there are lot of inner classes defined this creates some noise to the Coveralls reports. JaCoCo
> tracks inner classes within same source file so each source file is only reported once to
> Coveralls.

### Changelog

See [changelog](CHANGELOG.md) for more details.

### Migration

See [migration](MIGRATION.md) documentation for more information.

### Credits

- Jakub Bednář (@bednar) for Saga integration and the idea of chaining multiple reports provided
  by different coverage tools.
- Marvin Froeder (@velo) for Shippable and Appveyor support, configurable basedir and directory
  scanning source loader.
- Pasi Niemi (@psiniemi) for coverage merging from different reports to single source file.

### Continuous integration

Travis CI builds the plugin with Oracle JDK 7. All successfully built snapshots are deployed to
Sonatype OSS repository. Cobertura is used to gather coverage metrics and the report is submitted
to Coveralls with this plugin.

### Using test versions

Add the following repository configurations to your `pom.xml` to enable snapshot versions of this
plugin to be used.

```xml
  <repositories>
    <repository>
      <id>sonatype-nexus-snapshots</id>
      <url>https://oss.sonatype.org/content/repositories/snapshots</url>
      <releases><enabled>false</enabled></releases>
      <snapshots><enabled>true</enabled></snapshots>
    </repository>
  </repositories>
  <pluginRepositories>
    <pluginRepository>
      <id>sonatype-nexus-snapshot</id>
      <url>https://oss.sonatype.org/content/repositories/snapshots</url>
      <releases><enabled>false</enabled></releases>
      <snapshots><enabled>true</enabled></snapshots>
    </pluginRepository>
  </pluginRepositories>
```

### License

The project coveralls-maven-plugin is licensed under the MIT license.