In my opinion that's not a good reason and the majority of other libraries in maven don't do that. Is the first time I see a Scala library do that.
If every library would include the standard library, asides from the unnecessary bloating you have the problem that at runtime, when you mix different jars containing the same class you don't know which classes are going to be used (depends on the order of the jars) which can cause problems at runtime. If you need the Scala standard library you should add it to your dependency closure as any other library. https://mvnrepository.com/artifact/org.scala-lang/scala-library Providing an additional "assembly" or "fat jar" for convenience is ok, but I think the vanilla distribution should not include the standard library. Pedro. On Tue, Dec 4, 2018 at 8:18 PM Naveen Swamy <[email protected]> wrote: > > Pedro, > Not everyone has Scala installed on their system, especially for example > they are Java/Clojure users(and they don't have to). I don't expect them to > download/install Scala libraries. IMO, this approach is correct and lowers > the entry bar for users. > Soon, we are going include all dependencies of MXNet in the Jar and > publish, this is deliberately done. Hope that answers your concern. > > -Naveen > > On Tue, Dec 4, 2018 at 10:59 AM Chris Olivier <[email protected]> wrote: > > > Pedro, > > > > It would be polite to ask if there is a reason it is included before > > categorically declaring it is wrong. > > > > I am not involved in the scala library and what's included in it, but maybe > > there's a good reason for it. Or maybe there isn't. Either way, it's best > > to ask first :) > > > > Thanks, > > > > -Chris > >
