2
53%
master: 53%

Ran 05 Nov 2016 08:23PM UTC

Files 4

Run time 0s

Badge

Embed ▾

Committed 05 Nov 2016 08:12PM UTC coverage: 20.05% (-28.3%) from 48.387%

Job # 78.2

Build Type

push

travis-ci

Committed by

melix

Commit Message

Don't use the JMH CLI to execute JMH

So far the plugin used the JMH CLI options to execute benchmarks. The problem
is that the CLI options are not stable. This commit changes the implementation
so that we use the JMH API instead. This has several consequences:

- the plugin now builds using its own version of JMH
- a `runner.jar` is embedded and contains a minimal launcher for JMH benchmarks
- when the benchmarks are executed, we use the version provided by the user

In other words, to be able to use the JMH API, we're compiling against a version
of JMH which might not be the one that the user will use to compile the benchmarks
and execute them.

In general, this shouldn't be a problem, because the API is supposed to be stable.

Run Details

80 of 399 relevant lines covered (20.05%)

0.2 hits per line

melix / jmh-gradle-plugin / 78 / 2
53%
master: 53%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 78.2

melix / jmh-gradle-plugin / 78 / 2 53% master: 53%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 78.2

melix / jmh-gradle-plugin / 78 / 2
53%
master: 53%

README BADGES
x