-
Notifications
You must be signed in to change notification settings - Fork 120
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
Moving plugin release process to Bintray #961
base: master
Are you sure you want to change the base?
Conversation
5b4d543
to
fc446f0
Compare
befa1d2
to
7148e30
Compare
Right now on this pr, I get the following error when I run
I'm still looking into it. The fix might be making a separate MavenPublication for each plugin in the |
c57521a
to
cf55713
Compare
8752c98
to
91228eb
Compare
abbd010
to
d5e3642
Compare
d5e3642
to
2ad8078
Compare
This is on hold as we continue to explore alternative ways to deploy our products |
2ad8078
to
34d693b
Compare
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This pull request has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This pull request has been automatically detected as stale because it has not had recent activity and will be archived. Thank you for your contributions. |
Resolves #915 by moving the plugin artifact release process to Bintray. The work in this pr is largely based off of similar work done in
mapbox-gl-native
and in the Java SDK.