Dmytro Vyazelenko

@tmontgomery It is a question of compatibility between Java and C versions of the same code. Java ignores non-existing files whereas C fails with an error. Maybe we a new...

@baohuahuang1 Since #29 was implemented `jmh-gradle-plugin` is using bytecode generator. This means that annotation processor is **not** used anymore. I just did a quick test with simple `build.gradle` file: ```...

@srangwal how are you running benchmarks? Using `jmh` task or how?

Me and @aalmiray discussed this today. Plan is to finalize it next week. In a nutshell we want to provide a way to specify all JMH options in a single...

@mjpt777 it's a pity. I really hope next week we will make a new release with so much awaited fixes. Would love to hear what was not working for you...

@cursive-ide you need to enable `zip64` in order for jar task to succeed, i.e.: ``` gradle jmh { zip64 = true } ``` See also #18. Btw, packaging benchmarks into...

@cursive-ide FYI, since 0.3.0 release benchmarks are generated by `jmhCompileGeneratedClasses` task and compiled classes can be found inside `$project.buildDir/jmh-generated-classes` directory.

AFAIK this plugin does not natively support perfasm events but you can use one of the config parameters through which you can set JVM parameters, i.e. [see README](https://github.com/melix/jmh-gradle-plugin/blob/e4178504362852f71cb4d3ee96ff84b149c4abcd/README.adoc#configuration-options): ``` jmh...

It seems to be a problem with all `0.4.x` releases.

@sergey-morenets This seems to be the same issue as described in #89