Hi Abbass, Seeing the output from `sbt dependency-tree` from the sbt-dependency-graph plugin [1] might help. (caveat: I did not try this out; I don't know the state of maintenance)
Kenn [1] https://github.com/jrudolph/sbt-dependency-graph On Wed, Nov 9, 2016 at 6:33 AM, Jean-Baptiste Onofré <[email protected]> wrote: > Hi Abbass, > > As discussed together, it could be related to some changes we did in the > Maven profiles and build. > > Let me investigate. > > I keep you posted. > > Thanks ! > Regards > JB > > > On 11/09/2016 03:03 PM, amarouni wrote: > >> Hi guys, >> >> I'm facing a weird issue with a Scala project (using SBT/ivy) that uses >> *beam-runners-spark:0.3.0-incubating *which depends on >> *beam-sdks-java-core *& *beam-runners-core-java*. >> >> Until recently everything worked as expected i.e I had to declare a >> single dependency on *beam-runners-spark:0.3.0-incubating *which brought >> with it *beam-sdks-java-core *& *beam-runners-core-java*, but a couple >> of weeks ago I started having issues where the only workaround was to >> explicitly declare dependencies on *beam-runners-spark:0.3.0-incubating >> *in addition to its direct beam dependencies : *beam-sdks-java-core *& >> *beam-runners-core-java*. >> >> I verified that *beam-runners-spark's *pom contains both of the >> *beam-sdks-java-core *& *beam-runners-core-java *dependencies but still >> had to declare them explicitly, I'm not sure if this is an issue with >> SBT/ivy because Maven can correctly fetch the required beam dependencies >> but this issue appears only with beam dependencies. >> >> Did anyone with SBT/ivy encounter this issue. >> >> Thanks, >> >> Abbass, >> >> >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
