Thanks for raising this problem. There was a discussion about those issues and we came up with new policies for the Jira bot. At this point, we could close the JIRAs so that the bot won't create duplicate issues with the same version. https://lists.apache.org/[email protected]:lte=1M:%5BDISCUSS%5D%20Versioning%2C%20Hadoop%20related%20dependencies%20and%20enterprise%20users <https://lists.apache.org/[email protected]:lte=1M:%5BDISCUSS%5D%20Versioning%2C%20Hadoop%20related%20dependencies%20and%20enterprise%20users.>
Regards. Yifan On Mon, Sep 10, 2018 at 6:14 AM Jean-Baptiste Onofré <[email protected]> wrote: > +1 > > It would be great to be able to configure "known issues" ;) > > Regards > JB > > On 10/09/2018 15:07, Etienne Chauchot wrote: > > Hi, > > > > The bot for dependency checks opens tickets automatically when it sees > > staled dependencies. But in some cases it is perfectly normal. > > For example, in elasticsearchIO we have the core module (used by the > > users) that is compatible with all the versions (for backward > > compatibility and ease of use). But there is also one test module per > > supported version (v2, v5, v6) that runs tests against an embedded > > version of ES. These modules contain ES deps in v2, v5 and v6. > > In such a case the bot should not open a ticket. Shall we configure it > > with exceptions ? > > > > Note that for now I closed the related tickets. > > > > Best > > Etienne > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
