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.

Sign up for GitHub

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

Jump to bottom

Don't reference "compile" when it's not present #38

Open
Namnodorel opened this issue Apr 30, 2021 · 0 comments · May be fixed by #39
Open

Don't reference "compile" when it's not present #38

Namnodorel opened this issue Apr 30, 2021 · 0 comments · May be fixed by #39

Comments

@Namnodorel
Copy link

Namnodorel commented Apr 30, 2021 •
edited

In the latest Android Gradle Plugin Canary, compile has been removed in favor of implementation and api. That results in this line failing during build:

gradle-maven-plugin/artifact-pom-manager.gradle

Line 86 in c40e90e

configurations.compile.getDependencies().each { dep -> addDependency(dep, "compile") } 

Execution failed for task ':views:generatePomFileForMavenPublishPublication'.
> Could not apply withXml() to generated POM
   > Could not get unknown property 'compile' for configuration container of type org.gradle.api.internal.artifacts.configurations.DefaultConfigurationContainer.

I don't know much about Groovy syntax, but I think adding a check before accessing the property should quickly solve this problem.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Trying the compile configuration if possible andrewreeman/gradle-maven-plugin
1 participant
@Namnodorel