Re: [lucene] branch main updated: Always include errorprone dependency, even if we're not checking. This ensures consistent use patterns across JVMs.

> I know it's not needed, but "if" statements around dependencies look > strange to me! > It is just code, it's fine. That's the beauty of it. > I can try to merge it as a proof of concept. > You can have three remotes and cherry pick between repos. ;) This, amazingly, would work just fine. Uw

RE: [lucene] branch main updated: Always include errorprone dependency, even if we're not checking. This ensures consistent use patterns across JVMs.

: Always include errorprone dependency, even if we're not checking. This ensures consistent use patterns across JVMs. Should we maybe merge this also to Solr? I know it's not needed, but "if" statements around dependencies look strange to me! I can try to merge it as a proof

Re: [lucene] branch main updated: Always include errorprone dependency, even if we're not checking. This ensures consistent use patterns across JVMs.

Should we maybe merge this also to Solr? I know it's not needed, but "if" statements around dependencies look strange to me! I can try to merge it as a proof of concept. 😜 Uwe Am March 11, 2021 9:27:41 PM UTC schrieb dwe...@apache.org: >This is an automated email from the ASF dual-hosted git r