Move Java bindings to mozilla::java namespace

RESOLVED FIXED in Firefox 50

Status

()

defect
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: jchen, Assigned: jchen)

Tracking

unspecified
mozilla50
All
Android
Points:
---

Firefox Tracking Flags

(firefox50 fixed)

Details

Attachments

(3 attachments)

Moving the auto-generated bindings to mozilla::java avoids conflicts, and makes it more clear that we're using Java bindings in code.
Currently, auto-generated Java bindings are in the mozilla::widget
namespace, and that potentially conflicts with code under
widget/android. Moving the bindings to mozilla::java avoids conflicts
and makes it more clear that we're using Java bindings.
Attachment #8772599 - Flags: review?(snorp)
PrefsHelper uses Maybe<> as a replacement for a ternary expression, in
order to work around jni::StringParam's lack of copy constructor.
However, we can add a move constructor to StringParam, which lets us use
it in a ternary expression, and avoid the awkwardness of Maybe<>.
Attachment #8772601 - Flags: review+
Attachment #8772599 - Flags: review?(snorp) → review+

Comment 4

3 years ago
Pushed by nchen@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/0cf61343793a
Move Java bindings to mozilla::java namespace; r=snorp
https://hg.mozilla.org/integration/mozilla-inbound/rev/684888aeee81
Update existing code to use mozilla::java; r=me
https://hg.mozilla.org/integration/mozilla-inbound/rev/e954e5a93482
Improve usage of StringParam in PrefsHelper; r=me
backed this out for android bustage like https://treeherder.mozilla.org/logviewer.html#?job_id=32314092&repo=mozilla-inbound
Flags: needinfo?(nchen)
Repushed with clobber.
Flags: needinfo?(nchen)
You need to log in before you can comment on or make changes to this bug.