• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

vidal-community / jax-rs-linker
88%
master: 95%

Build:
Build:
LAST BUILD BRANCH: dependabot/maven/com.google.guava-guava-29.0-jre
DEFAULT BRANCH: master
Repo Added 27 Aug 2015 04:17PM UTC
Files 75
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH separate-api-and-processors
branch: separate-api-and-processors
CHANGE BRANCH
x
Reset
  • separate-api-and-processors
  • autostage
  • better_readme
  • dependabot/maven/com.google.guava-guava-29.0-jre
  • dependabot/maven/junit-junit-4.13.1
  • dev
  • issue_50
  • issue_51
  • issue_52
  • jacoco-full-report
  • java-8
  • master
  • originating-separation
  • v0.4.1
  • v1.0.0-M1

pending completion
290

push

travis-ci

jcgay
Separate api and processor implementation in two modules

It allows to not leak the processors to transitive dependencies.
The classes needed at runtime are separated in the 'api' module.

With Maven you should now use:

            <dependency>
                <groupId>fr.vidal.oss</groupId>
                <artifactId>jax-rs-linker-api</artifactId>
                <version>0.5-SNAPSHOT</version>
            </dependency>
            <dependency>
                <groupId>fr.vidal.oss</groupId>
                <artifactId>jax-rs-linker-processor</artifactId>
                <version>O.5-SNAPSHOT</version>
                <optional>true</optional>
            </dependency>

to import jax-rs-linker.

814 of 930 relevant lines covered (87.53%)

0.88 hits per line

Relevant lines Covered
Build:
Build:
930 RELEVANT LINES 814 COVERED LINES
0.88 HITS PER LINE
Source Files on separate-api-and-processors
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
290 separate-api-and-processors Separate api and processor implementation in two modules It allows to not leak the processors to transitive dependencies. The classes needed at runtime are separated in the 'api' module. With Maven you should now use: <dependency> ... push 15 Sep 2019 11:30AM UTC jcgay travis-ci pending completion  
291 separate-api-and-processors Separate api and processor implementation in two modules It allows to not leak the processors to transitive dependencies. The classes needed at runtime are separated in the 'api' module. With Maven you should now use: <dependency> ... Pull #60 15 Sep 2019 11:29AM UTC web-flow travis-ci pending completion  
289 separate-api-and-processors Separate api and processor implementation in two modules It allows to not leak the processors to transitive dependencies. The classes needed at runtime are separated in the 'api' module. With Maven you should now use: <dependency> ... Pull #60 15 Sep 2019 11:12AM UTC web-flow travis-ci pending completion  
288 separate-api-and-processors Separate api and processor implementation in two modules It allows to not leak the processors to transitive dependencies. The classes needed at runtime are separated in the 'api' module. With Maven you should now use: <dependency> ... push 15 Sep 2019 11:12AM UTC jcgay travis-ci pending completion  
285 separate-api-and-processors Separate api and processor implementation in two modules It allows to not leak the processors to transitive dependencies. The classes needed at runtime are separated in the 'api' module. With Maven you should now use: <dependency> ... Pull #60 15 Sep 2019 11:11AM UTC web-flow travis-ci pending completion  
284 separate-api-and-processors Separate api and processor implementation in two modules It allows to not leak the processors to transitive dependencies. The classes needed at runtime are separated in the 'api' module. With Maven you should now use: <dependency> ... push 15 Sep 2019 11:10AM UTC jcgay travis-ci pending completion  
282 separate-api-and-processors Separate api and processor implementation in two modules It allows to not leak the processors to transitive dependencies. The classes needed at runtime are separated in the 'api' module. With Maven you should now use: <dependency> ... push 15 Sep 2019 11:09AM UTC jcgay travis-ci pending completion  
283 separate-api-and-processors Separate api and processor implementation in two modules It allows to not leak the processors to transitive dependencies. The classes needed at runtime are separated in the 'api' module. With Maven you should now use: <dependency> ... Pull #60 15 Sep 2019 11:09AM UTC web-flow travis-ci pending completion  
280 separate-api-and-processors Separate api and processor implementation in two modules It allows to not leak the processors to transitive dependencies. The classes needed at runtime are separated in the 'api' module. With Maven you should now use: <dependency> ... push 15 Sep 2019 11:03AM UTC jcgay travis-ci pending completion  
281 separate-api-and-processors Separate api and processor implementation in two modules It allows to not leak the processors to transitive dependencies. The classes needed at runtime are separated in the 'api' module. With Maven you should now use: <dependency> ... Pull #60 15 Sep 2019 11:03AM UTC web-flow travis-ci pending completion  
See All Builds (145)
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc