Running benchmarks with groovy classes

Aleksey Shipilev aleksey.shipilev at oracle.com
Tue Feb 18 14:13:16 PST 2014


On 02/19/2014 02:07 AM, Aaron Tull wrote:
> Thanks for the fast response. As it turns out there is a gradle issue
> where the java compilation is done before the groovy compilation step.
> We declared a new sourceSet for benchmarking separate from the main or
> test sourceSet and the way we configured it was prone to this problem.
> Here is the gradle file and comments for the work around. 

Ah, that makes sense. You surely need to compile java sources as the
latest step after all other related code is already compiled and
accessible. I wouldn't call your way the "workaround", rather, this is
how I would expect it to work. :)

-Aleksey.


More information about the jmh-dev mailing list