Closed
Bug 1024714
Opened 10 years ago
Closed 10 years ago
Upgrade JDK used for Android builds from 1.6 to 1.7
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1043023
People
(Reporter: rnewman, Unassigned)
Details
For a number of reasons: * 1.6 hasn't seen public updates for over a year, skipping four private Sun/Apple releases including over a hundred security fixes. * There's some evidence that 1.6 doesn't build Fennec successfully on Mac (Bug 951968), or sometimes Linux (seen by Mike yesterday), so we would like to make configure barf when it sees an 8-year-old toolchain, saving developers a bunch of time. * Not coincidentally, almost all of our developers are building with JDK7 (and largely on Mac, which dropped JDK6 as a primary config in OS 10.6). Having large differences between developer configurations and build configurations is a recipe for pain. * Since the start of this year Android now supports some Java 7 language features, which we can only use when we have an up-to-date toolchain. What obstacles do we need to address before this can happen?
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•6 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•4 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•