It will have to wait until the release is complete, but yes, I’d like to get this in. Thanks for the patch Vladimir!
On Tue, Aug 11, 2020 at 04:38 Danny Chan <yuzhao....@gmail.com> wrote: > Michael, do you plan to push this function/patch ? We actually need this > too ~ > > Best, > Danny Chan > 在 2020年8月11日 +0800 AM3:06，Michael Mior <mm...@apache.org>，写道： > > Thanks for pointing back to the previous discussion. I'm fine with > > publishing separate modules. No real preference on my end since I > > haven't found consuming test artifacts to cause any problems. Although > > I'm not sure what the changes to the Gradle config would look like to > > support this. > > > > -- > > Michael Mior > > mm...@apache.org > > > > Le lun. 10 août 2020 à 14:49, Vladimir Sitnikov > > <sitnikov.vladi...@gmail.com> a écrit : > > > > > > Hi Michael, > > > > > > I suggest we go with adding explicitly published modules rather than > > > publishing tests. > > > Test artifacts do not have their own pom.xml, so they are not really > > > convenient for consumers. > > > > > > Here's the relevant thread: > > > > https://lists.apache.org/thread.html/2ab9652ea855dce0b5b75cc221a5f74ebec536818847ae5ce6d284f5%40%3Cdev.calcite.apache.org%3E > > > > > > I guess the naming could be calcite-testkit or calcite-test-framework. > > > > > > Vladimir > -- -- Michael Mior michael.m...@gmail.com
