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

Issues with Android Gradle Plugin 3.0 #136

Open
cfsbhawkins opened this issue Oct 30, 2017 · 2 comments
Open

Issues with Android Gradle Plugin 3.0 #136

cfsbhawkins opened this issue Oct 30, 2017 · 2 comments

Comments

@cfsbhawkins
Copy link

Ever since upgrading to android studio 3.0, the artifactoryPublish task has been broken. Two strange issues occur, one the POM is missing the dependencies, this could be related to the fact android no longer uses compile in the dependencies but, api or implementation. The other issue seems to be the artifactoryPublish task does not wait for all sub projects to finish and instead tries to run while other assemble tasks are still running, thus causing missing file errors on publish.

@billyjoker
Copy link

Hi @cfsbhawkins did you get resolve this issue?

@warnyul
Copy link

warnyul commented Apr 19, 2018

I have same problem maybe. I have a extended maven-publish plugin for publishing android artifacts. If I apply com.jfrog.artifactory plugin, I will get an error:
Configuration with name 'releaseRuntimeElements' not found.

The original issue found here: wupdigital/android-maven-publish#16

I think the problem occurs, because the artifactory plugin collects the publications too early. Before android plugin has resolved the android specific configurations.

I found this issue in 4.7.1, but its working correctly in 4.5.0

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

No branches or pull requests

3 participants