Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Plugin not working with bazel 0.26.0 (missing input file '@remote_java_tools_darwin//:Genclass') #845

Closed
natros opened this issue May 28, 2019 · 8 comments
Closed

Plugin not working with bazel 0.26.0 (missing input file '@remote_java_tools_darwin//:Genclass') #845

natros opened this issue May 28, 2019 · 8 comments
Assignees
@jin
Labels
topic: bazel Bazel integration (external repositories, aspects, flags, etc)

Comments

@natros
Copy link

natros commented May 28, 2019

Works from command link but not with intellij plugin. I have no problems with bazel 0.25.3

Syncing project: Sync (incremental)...
Updating VCS...
Running Bazel info...
Command: /usr/local/bin/bazel info --tool_tag=ijwb:IDEA:ultimate --curses=no --color=yes --progress_in_terminal_title=no --

Command: git diff --name-status --no-renames b5e7a496c71df57dbd277deaff615d0589ad3eaa

Computing VCS working set...
  .bazelproject (modified)
  .vscode/settings.json (added)
  candidaturas/BUILD.bazel (added)
  candidaturas/src/main/resources/pt/ipb/foo/conf.xml (added)
  docs/java/pt/ipb/docs/dto/UserDto.java (modified)

Sync targets from project view:
  //...:all

Sync targets from working set:
  //:all
  //candidaturas:all
  //docs/java/pt/ipb/docs/dto:all

Building blaze targets...
Command: /usr/local/bin/bazel build --tool_tag=ijwb:IDEA:ultimate --keep_going --build_event_binary_file=/var/folders/gk/1s9chv9j0291fhtc2dkpr6hh0000gn/T/intellij-bep-90bde706-21b7-4232-afce-d775d00c05fa --nobuild_event_binary_file_path_conversion --curses=no --color=yes --progress_in_terminal_title=no --aspects=@intellij_aspect//:intellij_info_bundled.bzl%intellij_info_aspect --override_repository=intellij_aspect=/Users/fsousa/Library/Application Support/IntelliJIdea2019.1/ijwb/aspect --output_groups=intellij-info-generic,intellij-info-java,intellij-info-py,intellij-resolve-java,intellij-resolve-py -- //...:all //:all //candidaturas:all //docs/java/pt/ipb/docs/dto:all

Loading: 
Loading: 0 packages loaded
Analyzing: 97 targets (0 packages loaded, 0 targets configured)
Analyzing: 97 targets (0 packages loaded, 0 targets configured)
INFO: Analyzed 97 targets (0 packages loaded, 0 targets configured).
INFO: Found 97 targets...
[2 / 6] [Prepa] BazelWorkspaceStatusAction stable-status.txt
ERROR: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/demo/java/pt/ipb/demo/dagger/example5/BUILD.bazel:1:1: //demo/java/pt/ipb/demo/dagger/example5:example5: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/wf/java/com/gitlab/natros/wf/guice/lifecycle/BUILD.bazel:1:1: //wf/java/com/gitlab/natros/wf/guice/lifecycle:lifecycle: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/docs/java/pt/ipb/docs/api/BUILD.bazel:1:1: //docs/java/pt/ipb/docs/api:api: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/demo/java/pt/ipb/demo/dagger/coffe/shopper/BUILD.bazel:1:1: //demo/java/pt/ipb/demo/dagger/coffe/shopper:shopper: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/demo/java/pt/ipb/demo/dagger/example2/BUILD.bazel:1:1: //demo/java/pt/ipb/demo/dagger/example2:example2: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/wf/java/com/gitlab/natros/wf/gwt/restygwt/BUILD.bazel:1:1: //wf/java/com/gitlab/natros/wf/gwt/restygwt:restygwt: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/demo/javatests/pt/ipb/demo/dagger/instance/BUILD.bazel:1:1: //demo/javatests/pt/ipb/demo/dagger/instance:BindInstanceTest: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/docs/java/pt/ipb/docs/ui/login/BUILD.bazel:1:1: //docs/java/pt/ipb/docs/ui/login:login: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/docs/java/pt/ipb/docs/ui/welcome/BUILD.bazel:1:1: //docs/java/pt/ipb/docs/ui/welcome:welcome: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/demo/java/pt/ipb/demo/dagger/example4/BUILD.bazel:1:1: //demo/java/pt/ipb/demo/dagger/example4:example4: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/wf/java/com/gitlab/natros/wf/gwt/core/BUILD.bazel:1:1: //wf/java/com/gitlab/natros/wf/gwt/core:core: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/demo/java/pt/ipb/demo/dagger/example3/BUILD.bazel:1:1: //demo/java/pt/ipb/demo/dagger/example3:example3: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/docs/java/pt/ipb/docs/api/gwt/BUILD.bazel:1:1: //docs/java/pt/ipb/docs/api/gwt:gwt: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/docs/java/pt/ipb/docs/ui/app/BUILD.bazel:1:1: //docs/java/pt/ipb/docs/ui/app:app: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/docs/java/pt/ipb/docs/server/user/BUILD.bazel:1:1: //docs/java/pt/ipb/docs/server/user:user: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/ipb/monorepo/demo/java/pt/ipb/demo/factory/BUILD.bazel:1:1: //demo/java/pt/ipb/demo/factory:factory: missing input file '@remote_java_tools_darwin//:Genclass'
INFO: Elapsed time: 1.750s, Critical Path: 0.00s
INFO: 0 processes.
FAILED: Build did NOT complete successfully
INFO: Build Event Protocol files produced successfully.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully
build invocation result: build_error
Sync was successful, but there were Bazel build errors. The project may not be fully updated or resolve until fixed. If the errors are from your working set, please uncheck 'Bazel > Sync > Expand Sync to Working Set' and try again.

$ bazel info
bazel-bin: /private/var/tmp/_bazel_fsousa/187058d15007c884f8885295a818c294/execroot/monorepo/bazel-out/darwin-fastbuild/bin
bazel-genfiles: /private/var/tmp/_bazel_fsousa/187058d15007c884f8885295a818c294/execroot/monorepo/bazel-out/darwin-fastbuild/bin
bazel-testlogs: /private/var/tmp/_bazel_fsousa/187058d15007c884f8885295a818c294/execroot/monorepo/bazel-out/darwin-fastbuild/testlogs
character-encoding: file.encoding = ISO-8859-1, defaultCharset = ISO-8859-1
command_log: /private/var/tmp/_bazel_fsousa/187058d15007c884f8885295a818c294/command.log
committed-heap-size: 578MB
execution_root: /private/var/tmp/_bazel_fsousa/187058d15007c884f8885295a818c294/execroot/monorepo
gc-count: 63
gc-time: 4460ms
install_base: /var/tmp/_bazel_fsousa/install/37d3a264d720ec9ae63603a543c8ff7c
java-home: /private/var/tmp/_bazel_fsousa/install/37d3a264d720ec9ae63603a543c8ff7c/_embedded_binaries/embedded_tools/jdk
java-runtime: OpenJDK Runtime Environment (build 11.0.2+7-LTS) by Azul Systems, Inc.
java-vm: OpenJDK 64-Bit Server VM (build 11.0.2+7-LTS, mixed mode) by Azul Systems, Inc.
max-heap-size: 3817MB
output_base: /private/var/tmp/_bazel_fsousa/187058d15007c884f8885295a818c294
output_path: /private/var/tmp/_bazel_fsousa/187058d15007c884f8885295a818c294/execroot/monorepo/bazel-out
package_path: %workspace%
release: release 0.26.0
repository_cache: /var/tmp/_bazel_fsousa/cache/repos/v1
server_log: /private/var/tmp/_bazel_fsousa/187058d15007c884f8885295a818c294/java.log.caronte.fsousa.log.java.20190528-123401.45561
server_pid: 45561
used-heap-size: 209MB
workspace: /Users/fsousa/Projects/ipb/monorepo

IntelliJ IDEA 2019.1.3 (Ultimate Edition)
Build #IU-191.7479.19, built on May 28, 2019
JRE: 11.0.2+9-b159.60 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.5
@natros natros changed the title Plugin not working with bazel 0.26.0 Plugin not working with bazel 0.26.0 (missing input file '@remote_java_tools_darwin//:Genclass') May 28, 2019
@jin
Copy link
Member

jin commented May 28, 2019

I cannot reproduce this on macOS with Bazel 0.26.0. This missing file belongs to an external repository that may have been updated between 0.25 and 0.26. It's odd that the external repository wasn't invalidated -- could you please try bazel clean --expunge and try again?

@jin jin added the topic: bazel Bazel integration (external repositories, aspects, flags, etc) label May 28, 2019
@natros
Copy link
Author

natros commented May 28, 2019

done that and the problem remains.

could you please teste this https://github.com/natros/bazel-maven:
git clone [email protected]:natros/bazel-maven.git
and see if you can reproduce the error. (it only happens inside intellij, works perfectly well from comand line)

...
[9 / 16] [Prepa] BazelWorkspaceStatusAction stable-status.txt
ERROR: missing input file '@remote_java_tools_darwin//:Genclass'
ERROR: /Users/fsousa/Projects/tmp/bazel-maven/java/com/gitlab/natros/test/BUILD.bazel:1:1: //java/com/gitlab/natros/test:foo: missing input file '@remote_java_tools_darwin//:Genclass'
....

@jin
Copy link
Member

jin commented May 29, 2019

Thanks for the repro! I can reproduce the error with this:

$ bazel build   --aspects=@intellij_aspect//:intellij_info_bundled.bzl%intellij_info_aspect \
  --override_repository=intellij_aspect="$HOME/Library/Application Support/IdeaIC2019.1/ijwb/aspect" \
  --output_groups=intellij-resolve-java -- //...:all

If you omit the intellij-resolve-java output group, it works fine.

@jin jin mentioned this issue May 29, 2019
Closed
@jin
Copy link
Member

jin commented May 29, 2019

Found the root cause: bazelbuild/bazel#8490

@jin jin self-assigned this May 29, 2019
@jin
Copy link
Member

jin commented May 29, 2019

This fix will be part of a patch release for 0.26

@jin jin mentioned this issue May 31, 2019
Closed
@jin jin reopened this May 31, 2019
@jin
Copy link
Member

jin commented May 31, 2019

Reopening until the patch fix for Bazel is out

@jin
Copy link
Member

jin commented Jun 1, 2019

More updates here bazelbuild/java_tools#8

@iirina iirina mentioned this issue Jun 3, 2019
Closed
bazel-io pushed a commit to bazelbuild/bazel that referenced this issue Jun 3, 2019
@iirina @copybara-github
Upgrade java_tools version to javac_11-v2.0
b0403a7 
Upgrade the java tools version in Bazel to `javac_11-v2.0`.

This PR fixes reported errors of `missing input file '@remote_java_tools_darwin//:Genclass'` (e.g. bazelbuild/intellij#845).

Also update the java_tools version for javac 9 and 10 that are used in tests. New java_tools releases for javac 9 and 10 were required because of new bazel API (`java_toolchain` now has an `jacocorunner` attribute).

The detailed release of `javac_11-v2.0` can be found in bazelbuild/java_tools#8.
The detailed release of java_tools `javac9-v2.0` and `javac10-v4.0` can be found in bazelbuild/java_tools#10.

Closes #8498.

PiperOrigin-RevId: 251245301
This was referenced Jun 3, 2019
Closed
Closed
iirina pushed a commit to iirina/bazel that referenced this issue Jun 4, 2019
@jin @iirina
Fix GenClass target label in java_tool's java_toolchain
7da078a 
Fixes bazelbuild/intellij#845

This causes IntelliJ resolution to fail when there's a `java_plugin` in the build.

The filegroup is `GenClass`, not `Genclass`.

```
filegroup(
    name = "GenClass",
    srcs = ["java_tools/GenClass_deploy.jar"],
)
```

This will require a new java_tools release and a patch release to 0.26.0.

Closes bazelbuild#8490.

PiperOrigin-RevId: 250487423
@iirina iirina mentioned this issue Jun 4, 2019
Closed
iirina pushed a commit to iirina/bazel that referenced this issue Jun 4, 2019
@jin @iirina
Fix GenClass target label in java_tool's java_toolchain
e3926fd 
Fixes bazelbuild/intellij#845

This causes IntelliJ resolution to fail when there's a `java_plugin` in the build.

The filegroup is `GenClass`, not `Genclass`.

```
filegroup(
    name = "GenClass",
    srcs = ["java_tools/GenClass_deploy.jar"],
)
```

This will require a new java_tools release and a patch release to 0.26.0.

Closes bazelbuild#8490.

PiperOrigin-RevId: 250487423
This was referenced Jun 4, 2019
Closed
Closed
aehlig added a commit to bazelbuild/bazel that referenced this issue Jun 4, 2019
@aehlig
Bump java_tools_javac10 from 3.1 to 3.2
55e4205 
This new java-tools release only contains the minimal changes with respect
to the previous release to fix bazelbuild/intellij#845
aehlig added a commit to bazelbuild/bazel that referenced this issue Jun 4, 2019
@aehlig
Bump java_tools_javac10 from 3.1 to 3.2
4c65832 
This new java-tools release only contains the minimal changes with respect
to the previous release to fix bazelbuild/intellij#845
bazel-io pushed a commit to bazelbuild/bazel that referenced this issue Jun 6, 2019
@aehlig
Release 0.26.1 (2019-06-06)
e6976fb 
Baseline: c2001a4

Cherry picks:

   + e67c961:
     Fix a non-determinism in create_embedded_tools.py.
   + 81aefe7:
     Remove unsupported cpu attribute from cc_toolchains.
   + 597e289:
     remote: made CombinedCache a composition of Disk and Http Cache
   + 942f7cf:
     C++: Fixes bug in C++ API with external repo aspects
   + 85a5a2b:
     Configure @androidsdk//:emulator_x86 and :emulator_arm to point
     to the unified emulator binary
   + 9835cb4:
     Automated rollback of commit
     844e4e2.
   + c963ba2:
     Windows, Python: fix arg. esc. also in host config
   + a1ea487:
     Do not pre-cache changed files under managed directories
   + 7dc78cd:
     Add explicit execution and target constraints for autodiscovered
     cc t?
   + dd9ac13:
     Fix a bug when a relative path is used for the execution log
   + 0ff19c6:
     Fix StandaloneTestStrategy.appendStderr
   + 7f49531:
     Fix the autodetecting Python toolchain on Mac
   + ddce723:
     Avoid exporting PATH unnecessarily
   + 35dd05a:
     Allow Starlark rules to be able to use the `exec_compatible_with`
   + cb82ed8:
     Release 0.26.0 (2019-05-28)
   + d1c0d20:
     Allow WORKSPACE file to be a symlink if no managed directories
     is used.
   + c3d2aa7:
     Fix ios, tvos and watchos arm64 constraints
   + 55e4205:
     Bump java_tools_javac10 from 3.1 to 3.2

Patch release on top of 0.26.0, fixing
- #8475
- #8520
- bazelbuild/intellij#845
@jin
Copy link
Member

jin commented Jun 6, 2019 •
edited
Loading

This is now fixed with Bazel 0.26.1.

@jin jin closed this as completed Jun 6, 2019
AlessandroPatti pushed a commit to uber-common/bazel that referenced this issue Jun 6, 2019
@aehlig
Release 0.26.1 (2019-06-06)
cfc6800 
Baseline: c2001a4

Cherry picks:

   + e67c961:
     Fix a non-determinism in create_embedded_tools.py.
   + 81aefe7:
     Remove unsupported cpu attribute from cc_toolchains.
   + 597e289:
     remote: made CombinedCache a composition of Disk and Http Cache
   + 942f7cf:
     C++: Fixes bug in C++ API with external repo aspects
   + 85a5a2b:
     Configure @androidsdk//:emulator_x86 and :emulator_arm to point
     to the unified emulator binary
   + 9835cb4:
     Automated rollback of commit
     844e4e2.
   + c963ba2:
     Windows, Python: fix arg. esc. also in host config
   + a1ea487:
     Do not pre-cache changed files under managed directories
   + 7dc78cd:
     Add explicit execution and target constraints for autodiscovered
     cc t?
   + dd9ac13:
     Fix a bug when a relative path is used for the execution log
   + 0ff19c6:
     Fix StandaloneTestStrategy.appendStderr
   + 7f49531:
     Fix the autodetecting Python toolchain on Mac
   + ddce723:
     Avoid exporting PATH unnecessarily
   + 35dd05a:
     Allow Starlark rules to be able to use the `exec_compatible_with`
   + cb82ed8:
     Release 0.26.0 (2019-05-28)
   + d1c0d20:
     Allow WORKSPACE file to be a symlink if no managed directories
     is used.
   + c3d2aa7:
     Fix ios, tvos and watchos arm64 constraints
   + 55e4205:
     Bump java_tools_javac10 from 3.1 to 3.2

Patch release on top of 0.26.0, fixing
- bazelbuild#8475
- bazelbuild#8520
- bazelbuild/intellij#845
irengrig pushed a commit to irengrig/bazel that referenced this issue Jun 18, 2019
@jin @irengrig
Fix GenClass target label in java_tool's java_toolchain
b339669 
Fixes bazelbuild/intellij#845

This causes IntelliJ resolution to fail when there's a `java_plugin` in the build.

The filegroup is `GenClass`, not `Genclass`.

```
filegroup(
    name = "GenClass",
    srcs = ["java_tools/GenClass_deploy.jar"],
)
```

This will require a new java_tools release and a patch release to 0.26.0.

Closes bazelbuild#8490.

PiperOrigin-RevId: 250487423
irengrig pushed a commit to irengrig/bazel that referenced this issue Jun 18, 2019
@iirina @irengrig
Upgrade java_tools version to javac_11-v2.0
4910bc1 
Upgrade the java tools version in Bazel to `javac_11-v2.0`.

This PR fixes reported errors of `missing input file '@remote_java_tools_darwin//:Genclass'` (e.g. bazelbuild/intellij#845).

Also update the java_tools version for javac 9 and 10 that are used in tests. New java_tools releases for javac 9 and 10 were required because of new bazel API (`java_toolchain` now has an `jacocorunner` attribute).

The detailed release of `javac_11-v2.0` can be found in bazelbuild/java_tools#8.
The detailed release of java_tools `javac9-v2.0` and `javac10-v4.0` can be found in bazelbuild/java_tools#10.

Closes bazelbuild#8498.

PiperOrigin-RevId: 251245301
irengrig pushed a commit to irengrig/bazel that referenced this issue Jun 18, 2019
@irengrig
Release 0.26.1 (2019-06-06)
6f5cae4 
Baseline: c2001a4

Cherry picks:

   + e67c961:
     Fix a non-determinism in create_embedded_tools.py.
   + 81aefe7:
     Remove unsupported cpu attribute from cc_toolchains.
   + 597e289:
     remote: made CombinedCache a composition of Disk and Http Cache
   + 942f7cf:
     C++: Fixes bug in C++ API with external repo aspects
   + 85a5a2b:
     Configure @androidsdk//:emulator_x86 and :emulator_arm to point
     to the unified emulator binary
   + 9835cb4:
     Automated rollback of commit
     844e4e2.
   + c963ba2:
     Windows, Python: fix arg. esc. also in host config
   + a1ea487:
     Do not pre-cache changed files under managed directories
   + 7dc78cd:
     Add explicit execution and target constraints for autodiscovered
     cc t?
   + dd9ac13:
     Fix a bug when a relative path is used for the execution log
   + 0ff19c6:
     Fix StandaloneTestStrategy.appendStderr
   + 7f49531:
     Fix the autodetecting Python toolchain on Mac
   + ddce723:
     Avoid exporting PATH unnecessarily
   + 35dd05a:
     Allow Starlark rules to be able to use the `exec_compatible_with`
   + cb82ed8:
     Release 0.26.0 (2019-05-28)
   + d1c0d20:
     Allow WORKSPACE file to be a symlink if no managed directories
     is used.
   + c3d2aa7:
     Fix ios, tvos and watchos arm64 constraints
   + 55e4205:
     Bump java_tools_javac10 from 3.1 to 3.2

Patch release on top of 0.26.0, fixing
- bazelbuild#8475
- bazelbuild#8520
- bazelbuild/intellij#845
irengrig pushed a commit to irengrig/bazel that referenced this issue Jul 15, 2019
@jin @irengrig
Fix GenClass target label in java_tool's java_toolchain
64aa89e 
Fixes bazelbuild/intellij#845

This causes IntelliJ resolution to fail when there's a `java_plugin` in the build.

The filegroup is `GenClass`, not `Genclass`.

```
filegroup(
    name = "GenClass",
    srcs = ["java_tools/GenClass_deploy.jar"],
)
```

This will require a new java_tools release and a patch release to 0.26.0.

Closes bazelbuild#8490.

PiperOrigin-RevId: 250487423
irengrig pushed a commit to irengrig/bazel that referenced this issue Jul 15, 2019
@iirina @irengrig
Upgrade java_tools version to javac_11-v2.0
97fd572 
Upgrade the java tools version in Bazel to `javac_11-v2.0`.

This PR fixes reported errors of `missing input file '@remote_java_tools_darwin//:Genclass'` (e.g. bazelbuild/intellij#845).

Also update the java_tools version for javac 9 and 10 that are used in tests. New java_tools releases for javac 9 and 10 were required because of new bazel API (`java_toolchain` now has an `jacocorunner` attribute).

The detailed release of `javac_11-v2.0` can be found in bazelbuild/java_tools#8.
The detailed release of java_tools `javac9-v2.0` and `javac10-v4.0` can be found in bazelbuild/java_tools#10.

Closes bazelbuild#8498.

PiperOrigin-RevId: 251245301
irengrig pushed a commit to irengrig/bazel that referenced this issue Jul 15, 2019
@irengrig
Release 0.26.1 (2019-06-06)
5d5105d 
Baseline: c2001a4

Cherry picks:

   + e67c961:
     Fix a non-determinism in create_embedded_tools.py.
   + 81aefe7:
     Remove unsupported cpu attribute from cc_toolchains.
   + 597e289:
     remote: made CombinedCache a composition of Disk and Http Cache
   + 942f7cf:
     C++: Fixes bug in C++ API with external repo aspects
   + 85a5a2b:
     Configure @androidsdk//:emulator_x86 and :emulator_arm to point
     to the unified emulator binary
   + 9835cb4:
     Automated rollback of commit
     844e4e2.
   + c963ba2:
     Windows, Python: fix arg. esc. also in host config
   + a1ea487:
     Do not pre-cache changed files under managed directories
   + 7dc78cd:
     Add explicit execution and target constraints for autodiscovered
     cc t?
   + dd9ac13:
     Fix a bug when a relative path is used for the execution log
   + 0ff19c6:
     Fix StandaloneTestStrategy.appendStderr
   + 7f49531:
     Fix the autodetecting Python toolchain on Mac
   + ddce723:
     Avoid exporting PATH unnecessarily
   + 35dd05a:
     Allow Starlark rules to be able to use the `exec_compatible_with`
   + cb82ed8:
     Release 0.26.0 (2019-05-28)
   + d1c0d20:
     Allow WORKSPACE file to be a symlink if no managed directories
     is used.
   + c3d2aa7:
     Fix ios, tvos and watchos arm64 constraints
   + 55e4205:
     Bump java_tools_javac10 from 3.1 to 3.2

Patch release on top of 0.26.0, fixing
- bazelbuild#8475
- bazelbuild#8520
- bazelbuild/intellij#845
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jin jin

Labels
topic: bazel Bazel integration (external repositories, aspects, flags, etc)
Projects
None yet
Milestone
No milestone
2 participants
@jin @natros