Re:Scala's version fragility makes the enterprise argument n...
by bad_user on Wednesday December 07, 2011 @05:02PM
(#3326288)
You have the source, but the Maven model used by the whole Java ecosystem for distribution/management of packages doesn't work like that. And replacing it with something else isn't a small feat.
[ Parent
| on HN ]
Re:Scala's version fragility makes the enterprise argument n...
by technomancy on Wednesday December 07, 2011 @05:16PM
(#3326374)
> You have the source, but the Maven model used by the whole Java ecosystem for distribution/management of packages doesn't work like that.
Oh, I don't know about that. Clojure does this; shipping source is default, and shipping bytecode is only done in cases of certain Java interop forms.
But Maven has a notion of "classifiers" that seem to be a good fit for this. I've seen them used to specify things like "this is the JDK 1.4-compatible version", so I wonder why Scala library authors haven't used them to publish the same artifact compiled against multiple versions of Scala.
Re:Scala's version fragility makes the enterprise argument n...
by dantheman on Wednesday December 07, 2011 @09:54PM
(#3327340)
Does clojure use maven for shipping source around?
Re:Scala's version fragility makes the enterprise argument n...
by technomancy on Thursday December 08, 2011 @01:37AM
(#3328017)
Yes, the source is just stored in jar files, which can contain any kind of files.