Closed
Bug 924617
Opened 11 years ago
Closed 11 years ago
Give JarMaker a "data" API
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla27
People
(Reporter: gps, Assigned: gps)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
37.53 KB,
patch
|
mshal
:
review+
|
Details | Diff | Splinter Review |
We'll want to hook up jar.mn processing to moz.build/emitter.py at some point so the build rules incurred from jar.mn are processed more efficiently, with proper dependencies. To do this, we'll need to give JarMaker a decent API for representing parsed results. Currently, parsing is mushed together with processing. Boo tight coupling!
|
Assignee | |
Comment 1•11 years ago
|
||
Just reformatting the code to make my life easier when I refactor it.
Attachment #814560 -
Flags: review?(mshal)
|
|
Assignee | |
Updated•11 years ago
|
Assignee: nobody → gps
|
||
Updated•11 years ago
|
Attachment #814560 -
Flags: review?(mshal) → review+
|
|
Assignee | |
Comment 2•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/a6a1f08b5561
Whiteboard: [leave open]
|
|
Assignee | |
Comment 4•11 years ago
|
||
This bug might be WONTFIX. Instead of letting in linger, I'm just going to close it. Will open new bug to track other jar.mn work.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [leave open]
Target Milestone: --- → mozilla27
|
||
Updated•6 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•