Skip to content

Remove merging of java_outputs in JavaPluginInfo.#14288

Closed
comius wants to merge 2 commits intobazelbuild:masterfrom
comius:java-plugin-info-regression
Closed

Remove merging of java_outputs in JavaPluginInfo.#14288
comius wants to merge 2 commits intobazelbuild:masterfrom
comius:java-plugin-info-regression

Conversation

@comius
Copy link
Copy Markdown
Contributor

@comius comius commented Nov 17, 2021

JavaPluginInfo merging of java_outputs caused a significant regression when a large number of plugins is present.

This value is not used by native code and it does not get exposed to Starlark. The only use case for java_outputs is IDE integrations, where the value is used from a single java_plugin target.

Fixes #14287

@Bencodes
Copy link
Copy Markdown
Contributor

Confirmed that this does reduce the heap significantly. #14287 (comment)

@comius comius marked this pull request as ready for review November 17, 2021 08:31
@comius comius requested a review from lberki as a code owner November 17, 2021 08:31
@bazel-io bazel-io closed this in 5cf1d6e Nov 17, 2021
Wyverald pushed a commit that referenced this pull request Nov 19, 2021
JavaPluginInfo merging of java_outputs caused a significant regression when a large number of plugins is present.

This value is not used by native code and it does not get exposed to Starlark. The only use case for java_outputs is IDE integrations, where the value is used from a single java_plugin target.

Fixes #14287

Closes #14288.

PiperOrigin-RevId: 410502716
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bazel HEAD OOMs during analysis phase when JavaPluginInfo provides Java outputs information

2 participants