New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 846440 link

Starred by 2 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Break apart chrome_java into smaller components

Project Member Reported by wnwen@chromium.org, May 24 2018

Issue description

This directly addresses our two top impacting dev issues:
1. Local Development Iteration Speed
2. Code Complexity / Technical Debt

This bug is to track the following:
1. Design doc on proposed components
2. Discussion and revisions on java@chromium.org
3. Implementation

Smaller targets mean that incremental builds will be faster (compiling smaller targets rather than all the code in chrome_java).

Separate components reduces the complexity of chrome_java as well as makes using Android's dynamic bundling easier.
 
Cc: wnwen@chromium.org pshmakov@chromium.org
Owner: ----
Status: Available (was: Assigned)
Making this available and +pshmakov@ as FYI

Splitting up chrome_java will likely involve Dagger on some level, as our dependencies are currently quite difficult to break and very densely connected. See visualizations in "Clank DevX" chat room (requires joining clank-developer-experience@ group).
Labels: DevX

Sign in to add a comment