jmh:compile doesnt work with 0.2.3 ? about sbt-jmh HOT 8 CLOSED

Hm, the project is tested using latest and we've also upgraded to it in Akka...
Is there any more details you could share? I'll look into it a bit later.

from sbt-jmh.

Thanks ! Few weeks back we upgraded to 0.2.2, that time there were no issues at all. We were using run and compile.
Until we upgraded yesterday (after seeing it in the Akka bench project). immediately noticed run needs to change to jmh:run and compile for jmh:compile. I tried clean ensured the .ivy2 caches with only proper version

We are on sbt 0.13.9, scala 2.11.7, jvm-1.8

from sbt-jmh.

Thanks for the hints, I don't see yet what might have gone wrong but will have a look. I'll keep you posted in this ticket.

from sbt-jmh.

One way to get around the issue was to add enablePlugins(JmhPlugin) to the root project in the build.sbt. Out benchmarks are not in the root project. This is not the case for 0.2.1 though it works fine.

from sbt-jmh.

Thanks a lot for the info! I'm a bit overwhelmed with tasks at the moment,
will try to investigate deeper as soon as I can. Thanks again for the
additional info, this helps a lot
On Aug 20, 2015 22:45, "Debajyoti Roλ" [email protected] wrote:

One way to get around the issue was to add enablePlugins(JmhPlugin) to
the root project in the build.sbt. Out benchmarks are not in the root
project. This is not the case for 0.2.1 though it works fine.

—
Reply to this email directly or view it on GitHub
#57 (comment).

from sbt-jmh.

I'm having the same issue.

I've got a public repo in which you can reproduce this, if you haven't been able to.

1. Check out: https://github.com/japgolly/nyaya.git It uses sbt-jmh 0.2.2.
2. sbt benchmark/run. 🌟 Everything works.
3. Change the version in project/plugins.sbt to 0.2.4.
4. sbt benchmark/run 💥
5. sbt benchmark/jmh:run 💥
6. sbt benchmark/jmh:compile 💥

from sbt-jmh.

I suggest you upgrade first - there's really no reason to stay on a old version like that, we're currently at 2.11.

from sbt-jmh.

Note that we don't guarantee any more compatibility than JMH does, please refer to JMH documentation and release notes for migrating up

from sbt-jmh.