I think it would be a big improvement to get rid of it. It's not how jars are supposed to be packaged and it has caused problems in many different context over the years.
For me a key step in moving away would be to fully audit/understand all compatibility implications of removing it. If other people are supportive of this plan I can offer to help spend some time thinking about any potential corner cases, etc. - Patrick On Wed, Sep 23, 2015 at 3:13 PM, Marcelo Vanzin <van...@cloudera.com> wrote: > Hey all, > > This is something that we've discussed several times internally, but > never really had much time to look into; but as time passes by, it's > increasingly becoming an issue for us and I'd like to throw some ideas > around about how to fix it. > > So, without further ado: > https://github.com/vanzin/spark/pull/2/files > > (You can comment there or click "View" to read the formatted document. > I thought that would be easier than sharing on Google Drive or Box or > something.) > > It would be great to get people's feedback, especially if there are > strong reasons for the assemblies that I'm not aware of. > > > -- > Marcelo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org > For additional commands, e-mail: dev-h...@spark.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
