Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closes #317: Use megazord-gradle plugin to consume single Application….. #318

Merged
merged 2 commits into from
Dec 20, 2018

Conversation

ncalexan
Copy link
Contributor

… Services native lib.

@ncalexan ncalexan requested a review from a team as a code owner November 30, 2018 22:36
@ncalexan
Copy link
Contributor Author

This won't pass yet 'cuz the companion plugin at https://github.com/mozilla/megazord-gradle hasn't been published. I'm working on that and not sure why it's delayed.

Copy link
Contributor

@csadilek csadilek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!


System.setProperty("mozilla.appservices.fxaclient_ffi_lib_name", "reference_browser");
System.setProperty("mozilla.appservices.logins_ffi_lib_name", "reference_browser");
System.setProperty("mozilla.appservices.places_ffi_lib_name", "reference_browser");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ncalexan looks like ReferenceBrowserComposition.init executes the same three setProperty calls. Are these leftovers?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The linter doesn't like the semicolons :).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes to both. I'm actually going to take the plugin in a different direction, which I just sketched docs (before implementing) in mozilla/application-services#463. Perhaps you could take a look, @csadilek? It's pretty close to what's happening here, and shouldn't require significant changes. It's just simpler for the plugin implementation and better for supporting unit testing transparently.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ncalexan read through it. Looks good to me!

@ncalexan ncalexan force-pushed the megazord branch 2 times, most recently from 5017dd4 to 5666249 Compare December 14, 2018 19:33
@ncalexan
Copy link
Contributor Author

@csadilek you looked at an earlier version of this (in a separate repo). I've put the plugin in appservices and reworked the internals significantly: it's simpler, you just declare the megazord you care about now. Can you take another look? Thanks!

This is busted in the wild just due to needing some publications to go out, so this will require an app-services bump in a-c. I'll get that in place.

@ncalexan
Copy link
Contributor Author

Just an update on this: the plugin is published and a-s v0.12.0 is published. Waiting to bump a-c (ticket link to follow) and then update this PR.

…n to consume single Application Services megazord native lib.
@ncalexan
Copy link
Contributor Author

I force-pushed to include some version and name changes, but there's nothing substantially different. I'll inspect the try results and if this is green and has the correct libraries included, I'll land it.

@ncalexan
Copy link
Contributor Author

Ah, I can't merge. In any case, based on the logs above, I think this ready to merge. I filed #354 to allow more authoritative testing.

@csadilek csadilek changed the title Closes #317: Use megazord-gradle plugin to consume single Application… Closes #317: Use megazord-gradle plugin to consume single Application…. Dec 20, 2018
@csadilek csadilek changed the title Closes #317: Use megazord-gradle plugin to consume single Application…. Closes #317: Use megazord-gradle plugin to consume single Application….. Dec 20, 2018
@csadilek
Copy link
Contributor

Rebased and tested this locally. Let's land this, build failures are network issues....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants