Tapio Rautonen

@ptahchiev if you still have the issue with JaCoCo and integration tests, you should try the latest `4.0.0-SNAPSHOT` version. I have set up JaCoCo unit and integration test setup in...

@stevendlander great catch. Java does not enforce to use same directory hierarchy than package name, but it is a generally accepted convention. The plugin relies on the same convention, otherwise...

Nice that you found a workaround (saved me the trouble of debugging this). There's not much I can do on the report parsing side to fix such issues. I could...

The problem is that this plugin cannot deal with any kind of code generation, because it requires the original source to be available. It is also questionable if you should...

@muzir this is interesting. I'm not totally sure how maven's runtime source loading works, but the plugin basically uses `MavenProject.getCompileSourceRoots()` so it "should" see the same sources as maven itself....

Is this still relevant? I haven't added support to Clover due to the fact that the tool is not free. I could ask Atlassian if I can use it for...

I think this feature is not documented as well as it should. The plugin tries to fetch build timestamp information from maven and by default it uses the property `${maven.build.timestamp}`...

@dtracers there is new feature that allows you to configure the plugin to use epoch timestamps for build time. Set `EpochMillis` in plugin configuration. This feature is not yet in...

I guess Travis Pro works like pretty much the same way as any private CI would work with the plugin. This means that you have to explicitly provide `repoToken` like...

@dbwiddis yea, sorry for being a bit slow on this. @PabloThiele is now a contributor in this project and will be doing the updates. I will help him out with...