Closed fleiber closed 3 years ago
Two different issues:
The jmhRuntime configuration has been deprecated for resolution
Explicitly set the duplicates strategy to 'DuplicatesStrategy.INCLUDE'
I think those issues have been fixed already, but as you make me doubt, I'm checking
id("me.champeau.gradle.jmh").version("0.5.2")
Do you by chance have a public build scan you can share?
(or a reproducer, because from the code I'm reading, the changes have made into 0.5.2 already)
Only jmh configuration applied:
jmh {
duplicateClassesStrategy = DuplicatesStrategy.EXCLUDE
}
Because otherwise build fails on Could not expand ZIP
: https://github.com/melix/jmh-gradle-plugin/issues/159#issuecomment-579705387
Thanks, this is helpful. yes I can reproduce the exclude strategy issue. But not the jmhRuntime
one for now :thinking:
Gradle version 6.8.1?
This looks simple to me:
'jmhRuntime'
runtime
is deprecated - https://docs.gradle.org/6.8.1/userguide/upgrading_version_5.html#dependencies_should_no_longer_be_declared_using_the_compile_and_runtime_configurations
https://github.com/melix/jmh-gradle-plugin/blob/master/src/main/groovy/me/champeau/gradle/JMHPlugin.groovy#L51 https://github.com/melix/jmh-gradle-plugin/blob/master/src/main/groovy/me/champeau/gradle/JMHPlugin.groovy#L300
The JMH plugin indeed creates a configuration named jmhRuntime
, but it's not the deprecated runtime
one, it's actually using the "correct" configurations (runtimeClasspath
):
So I'm quite confused as to why a deprecation warning is issued... And I'm using 7.0 for my tests.
Oh I think I understand what's going on. You get a deprecation warning in 6.8.1 because it uses an existing configuration, but in 7.0 it creates a new one so all is good. I'll rename it for clarity, it's a low risk breaking change.
Just released 0.5.3 which should fix those issues, thanks for your patience!
Just checked, LGTM. Thanks for your hard work!
This plugin still works with Gradle 6.x, but uses several deprecated features which are displayed as warning, which will break with Gradle 7.
This is reproduced by launching task jmh with Gradle 6.2 and plugin version 0.5.0.
Here are the Gradle log extracts:
For the second one, it happens multiple times, probably based on all the project dependencies having files with the same path name (so mostly in the standard META-INF folder).
P.S. BTW, jmh could be upgraded (last release is currently 1.23 against 1.21 defined in your plugin).
Thanks!