It's pretty much only third party plugins. I need it for the LDAP authenticator, and StratIO's lucene plugin will also need it. I know there are users out there with their own custom plugins that would benefit from it as well (and various other open source projects). It would make it easier, however it certainly is feasible for these devs to just build the jars themselves (and I've done this so far). If it's going to be easy I think there's value in generating and hosting nightly jars, but if it's difficult I can just write some docs for DIY.
On Thu, 20 Sep 2018 at 12:20, Mick Semb Wever <m...@apache.org> wrote: > Sorry about the terrible english in my last email. > > > > On the target audience: > > > > [snip] > > For developers building automation around testing and > > validation, it’d be great to have a common build to work from rather > > than each developer producing these builds themselves. > > > Sure. My question was only in context of maven artefacts. > It seems to me all the use-cases you highlight would be for the binary > artefacts. > > If that's the case we don't need to worry about publishing snapshots maven > artefacts, and can just focus on uploading nightly builds to > https://dist.apache.org/repos/dist/dev/cassandra/ > > Or is there a use-case I'm missing that needs the maven artefacts? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
