+1 for leaner distribution and a better 'download' webpage. +1 for a full distribution if we can automate it besides supporting the leaner one. If we support both, I'd image release managers should be able to package two distributions with a single change of parameter instead of manually package the full distribution. How to achieve that needs to be evaluated and discussed, probably can be something like 'mvn clean install -Dfull/-Dlean', I'm not sure yet.
On Wed, Jan 23, 2019 at 10:11 AM Thomas Weise <t...@apache.org> wrote: > +1 for trimming the size by default and offering the fat distribution as > alternative download > > > On Wed, Jan 23, 2019 at 8:35 AM Till Rohrmann <trohrm...@apache.org> > wrote: > >> Ufuk's proposal (having a lean default release and a user convenience >> tarball) sounds good to me. That way advanced users won't be bothered by >> an >> unnecessarily large release and new users can benefit from having many >> useful extensions bundled in one tarball. >> >> Cheers, >> Till >> >> On Wed, Jan 23, 2019 at 3:42 PM Ufuk Celebi <u...@apache.org> wrote: >> >> > On Wed, Jan 23, 2019 at 11:01 AM Timo Walther <twal...@apache.org> >> wrote: >> > > I think what is more important than a big dist bundle is a helpful >> > > "Downloads" page where users can easily find available filesystems, >> > > connectors, metric repoters. Not everyone checks Maven central for >> > > available JAR files. I just saw that we added a "Optional components" >> > > section recently [1], we just need to make it more prominent. This is >> > > also done for the SQL connectors and formats [2]. >> > >> > +1 I fully agree with the importance of the Downloads page. We >> > definitely need to make any optional dependencies that users need to >> > download easy to find. >> > >> >
