we have a maven corporate repository inhouse and of course we also use
maven central. sbt can handle retrieving from and publishing to maven
repositories just fine. we have maven, ant/ivy and sbt projects depending
on each others artifacts. not sure i see the issue there.
On Tue, Mar 11, 2014 at
Asm is such a mess. And their suggested solution being everyone should
shade it sounds pretty awful to me (not uncommon to have shaded asm 15
times in a single project). But I guess it you are right that shading is
only way to deal with it at this point...
On Mar 11, 2014 5:35 PM, Kevin Markey
dependencySet, but provided will mark the entire dependency tree as
excluded. It is also possible to exclude jar by jar, but this is
pretty error prone and messy.
On Tue, Feb 25, 2014 at 2:45 PM, Koert Kuipers ko...@tresata.com
wrote:
yes in sbt assembly you can exclude jars (although i never had a
need
associated with manual
translation of dependency specs from one system to another, while
still maintaining the things which are hard to translate (plugins).
On Wed, Feb 26, 2014 at 7:17 AM, Koert Kuipers ko...@tresata.com
wrote:
We maintain in house spark build using sbt. We have
github is not aware of the new repo being a base-fork, so its not easy to
re-point pull requests. i am guessing it didnt get cloned from the
incubator spark one?
On Wed, Feb 26, 2014 at 5:56 PM, Patrick Wendell pwend...@gmail.com wrote:
Sorry if this wasn't clear - If you are in the middle of
201 - 205 of 205 matches
Mail list logo
