For implementing this in practice, we could also extend our CI pipeline a bit, and count the number of deprecation warnings while compiling Flink. We would hard-code the current number of deprecations and fail the build if that number increases.
We could actually extend this and run a curated list of IntelliJ inspections during the build (IIRC this was discussed in the past): https://www.jetbrains.com/help/idea/command-line-code-inspector.html On Wed, Jul 14, 2021 at 11:14 AM Chesnay Schepler <ches...@apache.org> wrote: > It may be better to not do that to ease the migration to junit5, where > we have to address exactly these usages. > > On 14/07/2021 09:57, Till Rohrmann wrote: > > I actually found > > myself recently, whenever touching a test class, replacing Junit's > > assertThat with Hamcrest's version which felt quite tedious. > > >
