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

x/mobile: consider androidstudio gobind plugin retirement #25314

Closed
hyangah opened this issue May 9, 2018 · 3 comments
Closed

x/mobile: consider androidstudio gobind plugin retirement #25314

hyangah opened this issue May 9, 2018 · 3 comments
Labels
Milestone

Comments

@hyangah
Copy link
Contributor

@hyangah hyangah commented May 9, 2018

Working with the gradle plugins is a pain, we have no active maintainer for this plugin.
The release process is not well-established (#14690).
Maintenance burden seems to outweigh the benefit.

Users can manually build the .aar file with gomobile and import the .aar file into the studio without the plugin.

@eliasnaur

@hyangah hyangah added the mobile label May 9, 2018
@hyangah hyangah added this to the Unreleased milestone May 9, 2018
@hyangah hyangah changed the title mobile: consider androidstudio gobind plugin retirement x/mobile: consider androidstudio gobind plugin retirement May 9, 2018
@eliasnaur

This comment has been minimized.

Copy link
Contributor

@eliasnaur eliasnaur commented May 9, 2018

I'm for this proposal.

What happens with the released plugin? If we don't delete it, users will mistakenly expect it to work and be supported.

@gopherbot

This comment has been minimized.

Copy link

@gopherbot gopherbot commented Oct 10, 2018

Change https://golang.org/cl/141057 mentions this issue: misc,example/bind/hello: remove the Gradle plugin

zchee pushed a commit to zchee/golang-wiki that referenced this issue Jan 28, 2019
…aintainer: golang/go#25314. Users are probably better off without it.
@prep

This comment has been minimized.

Copy link

@prep prep commented Aug 1, 2019

Apologies for commenting in a closed ticket, but it's a bit unclear to me how the plugin-specific functionality (like databinding and R/layout generation) from the plugin is replaced. Is there an alternative way to go about this, or should I consider the removal of the plugin and the reverse example as a hint that Android support via reverse bindings is being depreciated?

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

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.