Closed allanlewis closed 5 years ago
I think this is actually due to the use of that method in mkobit/jenkins-pipeline-shared-library-example
, perhaps this issue should be moved to that repo?
I believe this should be fixed by https://github.com/mkobit/jenkins-pipeline-shared-libraries-gradle-plugin/pull/91 and will be released in the next version (0.10.0
) of the plugin
https://github.com/mkobit/jenkins-pipeline-shared-libraries-gradle-plugin/pull/96 looks like the last one, I'll release it as 0.10.1
I think 0.10.1
has resolved this, I don't believe I see any deprecation warnings after pushing https://github.com/mkobit/jenkins-pipeline-shared-libraries-gradle-plugin/commit/cd5f95c2fefa51066d4ec2292e4b659ed61e3b0b
When I run any Gradle command from
master
(eef1ea2), I get the following warning:If I re-run with
--warning-mode all
, I get the following output:If I upgrade Gradle to the latest version, 5.2, I get the same warnings.