No, it's not even looking.
Very interesting ivy file generated by sbt where neither dependencies have
"compile" conf.
<dependency org="org.apache.beam" name="beam-sdks-java-core" rev=
"0.3.0-incubating" force="true" conf="test->runtime(*),master(compile)">
<artifact name="beam-sdks-java-core" type="jar" ext="jar" conf="test"/>
<artifact name="beam-sdks-java-core" type="jar" ext="jar" conf="test" m:
classifier="tests"/>
<exclude org="org.slf4j" module="slf4j-jdk14" name="*" type="*" ext=
"*" conf="" matcher="exact"/>
</dependency>
<dependency org="org.apache.beam" name="beam-runners-core-java" rev=
"0.3.0-incubating" force="true" conf="test->runtime(*),master(compile)">
<exclude org="org.slf4j" module="slf4j-jdk14" name="*" type="*" ext="*"
conf="" matcher="exact"/>
</dependency>
On Thu, Nov 10, 2016 at 7:51 PM Amit Sela <amitsel...@gmail.com> wrote:
> @Abbass/Manu does SBT state that it's looking for *beam-sdks-java-core *&
> *beam-runners-core-java* but fails to find them ?
>
> On Thu, Nov 10, 2016 at 3:43 AM Manu Zhang <owenzhang1...@gmail.com>
> wrote:
>
> > Hi all,
> >
> > I tried and reproduced the issue. "sbt-dependency-graph" doesn't show
> > beam-sdks-java-core
> > and beam-runners-core-java either.
> > It's likely an ivy/sbt issue. I'll dig further.
> >
> > Manu
> >
> > On Thu, Nov 10, 2016 at 3:07 AM Kenneth Knowles <k...@google.com.invalid>
> > wrote:
> >
> > > 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é <j...@nanthrax.net>
> > > 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é
> > > > jbono...@apache.org
> > > > http://blog.nanthrax.net
> > > > Talend - http://www.talend.com
> > > >
> > >
> >
>
