(Wouldn't it be nice if we had a "Build & Test" component, rather than just "Test"?)

(In reply to Richard Newman [:rnewman] from comment #0) > (Wouldn't it be nice if we had a "Build & Test" component, rather than just > "Test"?) When I requested Test, I figured we would grow a "Build" component if and when it was necessary :) This is relevant to my interests. The "right" way to do this is not entirely clear. The Android platform has grown a few different "library APK" features that I think allow for this; one of them is Android ARchives (.aar) files, but I've never prioritized looking into them. If we're getting serious about shipping GeckoView, we should do that build system work.

See bug 927388

I should clarify that including only a subset of resources in the shipped GeckoView library code is going to fly. The GeckoView libraries are compiled with an org.mozilla.gecko.R class defining the full set of resources IDs. Monkeying with the shipped resources invalidates those resources IDs in difficult to control ways. Don't do that.

(In reply to Nick Alexander :nalexander PTO until Dec 7th from comment #3) > I should clarify that including only a subset of resources in the shipped > GeckoView library code is going to fly. is *not* going to fly.

Move some old bugs with `[geckoview]` in their summary to the GeckoView Bugzilla component.

This is no longer relevant -- now that we build GeckoView as a separate Gradle project, we're not shipping Fennec Android resources with GV: https://bugzilla.mozilla.org/show_bug.cgi?id=1291363. Of course, the omnijar is still terribly bloated! https://bugzilla.mozilla.org/show_bug.cgi?id=1351000 and friends start to address this.