...
- If you are not working on Python, the simplest solution is to not build it, i.e. only build the module that you're interested in.
- If you do need to build Python, follow the instructions here: Set up IntelliJ for Python development
Cannot resolve vendored artifacts (org.apache.beam.vendor.[xyz])
This isn't a build error, but the IntelliJ code editor will show red squigglies and fail to to symbol completion for vendored artifacts.
This is a short-coming of the Gradle IntelliJ plugin (see IDEA-197980). Because we produce the repackaged artifact and consume it as a dependency within a single multi-project Gradle build, IntelliJ fails when trying to resolve sources. This has been discussed repeatedly on the dev@ list, but no solution yet exists.
- (Jul 2018) Vendoring / Shading Protobuf and gRPC
- (Aug 2018) Status of IntelliJ with Gradle
- (Oct 2018) Re: Does anybody have a strong intellij setup?
- (Oct 2018) [DISCUSS] Publish vendored dependencies independently
Note that this is only an IntelliJ issue; the build works just fine from the command-line. Improving this behavior in IntelliJ is tracked via
| Jira | ||||||
|---|---|---|---|---|---|---|
|
Compilation failed with exit code 1; see the compiler error output for details.
...