JavaInfo starlark constructor doesn't fill compilation_info member

[ittaiz]

Description of the problem / feature request:

JavaInfo instances created from starlark have a None value in compilation_info

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

bazelbuild/rules_scala#872

What's the output of bazel info release?

1.1.0

Any other information, logs, or outputs that you want to share?

Two important notes:

1. This is blocking moving IntelliJ plugin to use JavaInfo provider instead of the scala attribute.
   https://github.com/bazelbuild/intellij/blob/master/aspect/intellij_info_impl.bzl#L505
   https://github.com/bazelbuild/intellij/blob/master/aspect/java_classpath.bzl#L22
2. This also means incompatible_disable_target_provider_fields: disallow access of providers on "target" objects by field syntax #9014 is blocked since we can't move to providers without IntelliJ support and I think they need the compilation_info member for that (but I might be wrong). cc @brendandouglas as an expert of whether or not IJ can use other data from the JavaInfo provider is compilation_info is None

[ittaiz]

cc @iirina

[ittaiz]

I took a look and it's not actually blocking the move to attribute since IJ can just use target[JavaInfo].transitive_runtime_jars for now

[brendandouglas]

+1 -- this is important for IntelliJ support (and for any non-native java rules). We'll workaround it in the short-term, but I think it's very important to fix this on the Bazel side.

[ittaiz]

@aiuto @iirina any ideas when this will be triaged?

[suman-ganta]

Ran into this. Wondering if this is being addressed?

[comius]

It is, see https://docs.google.com/document/d/10isTEK5W9iCPp4BIyGBrLY5iti3Waaam6EeGVSjq3r8/edit
compilation_info is being removed from JavaInfo, as far as I know IntelliJ aspect is already not using it.

[github-actions]

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.

[github-actions]

This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team (@bazelbuild/triage). Thanks!