Hi, Thanks all for the prompt response! That helps a lot.
I seem to have managed to sort it out. What worked for me was to manually change Dependencies for runners/spark/main project (which I've been interested in) and remove 5 directory-based 2.20.0-SNAPSHOT-versioned dependencies, e.g. /Users/jacek/dev/oss/beam/sdks/java/core/build/libs/beam-sdks-java-core-2.20.0-SNAPSHOT.jar (/Users/jacek/dev/oss/beam is where I git clone the repo). I also added a Module Dependency on Module: 'beam.sdks.java.core.main'. That's however a temporary solution since Reimporting / Reloading the project in Gradle view makes all the changes go away :( No idea how to do it properly as I'm a Gradle noob. Pozdrawiam, Jacek Laskowski ---- https://about.me/JacekLaskowski "The Internals Of" Online Books <https://books.japila.pl/> Follow me on https://twitter.com/jaceklaskowski <https://twitter.com/jaceklaskowski> On Wed, May 20, 2020 at 6:01 PM Nathan Fisher <nfis...@junctionbox.ca> wrote: > I was running into similarish problems. I’m not sure if I’m breaking > something by building in terminal and IntelliJ. After a while the check > task fails for sdks/java being unable to resolve jar dependencies. > > There were a bunch of artefacts this happened with like Avro-x.y.z-test > and a shaded Cassandra core. It fails saying the artefact can’t be found in > maven repos nor the local .m2 repository cache. I haven’t figured out a > reproducible test case as to how it gets into this state. > > It seems to either imply a dependency relationship is missing and the > build DAG isn’t able to order the build targets correctly, or I have a > unique snowflake setup, or being new to gradle I’m missing a trick that’s > obvious to a gradle veteran. > > The most consistent way I’ve figured to recover from the situation is move > the .m2/repository out of the way, create a new empty directory, and > rebuild. > > On Wed, May 20, 2020 at 11:22, Omar Ismail <omarism...@google.com> wrote: > >> Hey Jacek, >> >> What I usually do is `git clone REPO` in a new folder, and then in the >> Intellij main menu I press "Open", navigate to that folder, then press >> "Open". Gradle then automatically starts doing the build. >> >> Hope this helps! >> C >> Best, >> Omar >> >> On Wed, May 20, 2020 at 10:06 AM Jacek Laskowski <ja...@japila.pl> wrote: >> >>> Hi, >>> >>> I've been trying to import the Beam sources to IntelliJ IDEA for some >>> time now and must admit I'm very surprised how painful it is. >>> >>> I tried the steps described in >>> https://cwiki.apache.org/confluence/display/BEAM/Set+up+IntelliJ+from+scratch, >>> but the wizards give me different options (perhaps I'm on a newer IDEA or >>> could it be attributed to macOS?) >>> >>> Import is successful, but the modules don't seem to have dependencies >>> specified and SparkRunner has all org.apache.beam.sdk. imports unresolved >>> (Cannot resolve the symbol 'XXX'). >>> >>> I'm sure I'm missing something obvious and simple, but seems it's too >>> obvious and too simple for me today :( Thanks for any hints. >>> >>> Pozdrawiam, >>> Jacek Laskowski >>> ---- >>> https://about.me/JacekLaskowski >>> "The Internals Of" Online Books <https://books.japila.pl/> >>> Follow me on https://twitter.com/jaceklaskowski >>> >>> <https://twitter.com/jaceklaskowski> >>> >> >> >> -- >> >> Omar Ismail | Technical Solutions Engineer | omarism...@google.com | >> > -- > Nathan Fisher > w: http://junctionbox.ca/ >
