bazelbuild/rules_android

Support customizing toolchain level jvm_flags

Open

#141 opened on Sep 13, 2023

View on GitHubContributor guide
 (3 comments) (1 reaction) (0 assignees)Java (88 forks)auto 404
P3good first issue

Repository metrics

Stars
 (202 stars)
PR merge metrics
 (PR metrics pending)

Description

Users are unable to easily customize the jvm_flags backing some of the tools in toolchain.bzl as they are all being passed as their raw deploy jars instead of their executable Bazel types.

This means that JVM resource tuning changes like https://github.com/bazelbuild/rules_android/pull/140 will always need to be checked into rules_android or kept in forks rather than leveraging the existing attributes that Bazel provides.

Contributor guide

Research direction
Modify toolchain.bzl to pass jvm flags via Bazel executable attributes instead of raw deploy jars, allowing users to customize flags without modifying rules android.
Tech stack
java
Domain
build system
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
BazelJava
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30