I had forgotten about that page. I think it is a good idea to include it in the release process. I would rephrase the page a little bit to make it clear that dependency conflicts are normal and expected in Java so this is an FYI page about the versions we test with. Users may have to pin to other versions, and that is normal too.
We can scrape some of this from the gradle script source code. It would be better to use the output of some Gradle command to list the deps. But since Beam is a collection of many, many modules that could be a lot of trouble. Kenn On Sun, Mar 24, 2019 at 10:37 AM David Morávek <[email protected]> wrote: > Hello, > > I've run into java-dependencies page > <https://beam.apache.org/documentation/sdks/java-dependencies/>, while > upgrading joda-time. This page is supposed to track dependencies across > releases, but the last entry is for 2.9 release. > > Do we still want to maintain this? If so, could we somehow include it in > the release process? > > Also we should add missing entries for 2.10 and 2.11, is there any script > I can use to generate this? > > D. >
