+1, I considered it a necessary evil -- Regards, Konstantin Orlov
> On 5 Aug 2021, at 16:37, Alexei Scherbakov <alexey.scherbak...@gmail.com> > wrote: > > +1 > > чт, 5 авг. 2021 г. в 16:12, Alexander Polovtcev <alexpolovt...@gmail.com>: > >> Hello, dear Igniters! >> >> I would like to discuss the possibility of using Guava >> <https://github.com/google/guava> in Ignite 3. I know about the >> restrictive >> policy of using it in Ignite 2, but I have the following reasons: >> >> 1. We are de-facto using it already as an implicit dependency, since the >> Calcite module depends on it, and Calcite is going to stay for a while =) >> 2. AFAIK, the "bytecode" module is copied into the codebase only to strip >> Guava away from it. We can remove this module, which will improve the >> maintainability of the project. >> 3. We have some copy-paste of Guava code in the project. For example, see >> this >> < >> https://github.com/apache/ignite-3/blob/main/modules/core/src/main/java/org/apache/ignite/internal/util/IgniteUtils.java#L136 >>> >> and this >> < >> https://github.com/apache/ignite-3/blob/main/modules/core/src/main/java/org/apache/ignite/internal/util/IgniteUtils.java#L428 >>> >> . >> 4. Regarding security concerns, this report >> <https://www.cvedetails.com/product/52274/Google-Guava.html?vendor_id=1224 >>> >> shows no major vulnerability issues for the last three years. >> >> Taking these points into account, I propose to allow using Guava both in >> production and test code and to add it as an explicit dependency. >> >> What do you think? >> >> -- >> With regards, >> Aleksandr Polovtcev >> > > > -- > > Best regards, > Alexei Scherbakov
