Re: [Proposal] Automation For Beam Dependency Check

This kind of leaking analysis that `mvn dependency:analyze` does is I think what is also called IWYU (Include What You Use). I looked around and there are some gradle plugins to do the same thing. I couldn't tell which was the most robust. Kenn On Mon, Jun 4, 2018 at 9:46 AM Chamikara Jayalath

Re: [Proposal] Automation For Beam Dependency Check

On Mon, Jun 4, 2018 at 6:10 AM Ismaël Mejía wrote: > Is there a way to add to that weekly report the new dependencies that > were introduced in the week before, or that have changed? > I think it makes sense to add a recent changes section so that community is up to date and can discuss if

Re: [Proposal] Automation For Beam Dependency Check

Is there a way to add to that weekly report the new dependencies that were introduced in the week before, or that have changed? We are not addressing another important problem: Leaking of dependencies. I am not aware of the gradle equivalent of the maven dependency plugin that helps to determine

Re: [Proposal] Automation For Beam Dependency Check

Thanks everyone for making comments and suggestions. I modified the proposal that added dependency release time as the major criteria for outdated package determination. The revised doc is here: https://docs.google.com/document/d/1rqr_8a9NYZCgeiXpTIwWLCL7X8amPAVfRXsO72BpBwA. Any comments are

Re: [Proposal] Automation For Beam Dependency Check

Thanks Yifan. Added some comments. I think having regularly generated human reports on outdated decencies of Beam SDKs will be extremely helpful in keeping Beam in a healthy state. - Cham On Thu, May 24, 2018 at 7:08 AM Yifan Zou wrote: > Hello, > > I have a proposal to