Closed dadoonet closed 6 years ago
@jasontedor Did #27305 fully take care of this? Anything for @mgreau to do here?
No, there is more work to do here. Namely:
Gradle now uses separate output directories for each JVM language, but this build assumes a single directory for all classes from a source set. This behaviour has been deprecated and is scheduled to be removed in Gradle 5.0
at build_a92y8m4ak5gicu9a6zp2j6xfn.run(/Users/dpilato/Documents/Elasticsearch/dev/elasticsearch/es-master/elasticsearch/benchmarks/build.gradle:31)
(Run with --stacktrace to get the full stack trace of this deprecation warning.)
We know this need to be done and we will cross it when we need to. Im closing this issue as its not really a bug report but more of a "we need to do X", which is known.
When building today the project with Gradle 4.3, I saw tons of deprecated logs and I think we should prepare ourselves for Gradle 5.0.
This one appeared already in previous versions:
The following ones are new I believe (4.2 or 4.3):
The following ones are also about naming but a bit different: