I was looking at this recently to try and figure out how to generate this in a reliable way for Java, but hadn't come up with a clean solution yet. For the related Python dependencies page [1], I recently wrote a script that scrapes the dependencies and generates an HTML table that can be copied into the markdown file, and I updated the page with deps info up to 2.11.0. I need to do some cleanup on the script, and then I will add it to the repo. With that, it could be made part of the release process for the Python side of things.
[1] https://beam.apache.org/documentation/sdks/python-dependencies/ On Sun, Mar 24, 2019 at 9:21 PM Kenneth Knowles <k...@apache.org> wrote: > 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 <d...@apache.org> 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. >> >
