@posco @marius @squarecog right, or I’ll know to not upgrade until I have time to fix compatibility. It’s about reducing surprise.
-
-
@avibryant@marius@posco@slyphon@squarecog in theory you could do that from maven central as each artifact publishes its deps and source. -
@J_@marius@posco@slyphon@squarecog I want to be able to switch smoothly between source artifact, github repo, local checkout... -
@avibryant@marius@posco@slyphon@squarecog for projects on github and maven central the Pom contains the git URL. releases are tagged
End of conversation
New conversation -
-
-
@avibryant@posco@slyphon@squarecog absolutely. -
@marius@avibryant@posco@slyphon@squarecog SBT took an honest swing at that. As you might expect, results were mixed -
@mccv@avibryant@posco@slyphon@squarecog (cf. BSD ports where you have a standard metadata format for sources) -
@marius@mccv@avibryant@posco@slyphon@squarecog Still, though, "pull down these JARs and get them on your classpath" has strong appeal -
@jerrykuch@mccv@avibryant@posco@slyphon@squarecog other good examples are OPAM (OCaml) or Go’s build system. -
@marius@mccv@avibryant@posco@slyphon@squarecog Reassures on "saving Scala even if it becomes a binary incompatibility disaster" front.
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.