-
Notifications
You must be signed in to change notification settings - Fork 160
[Gradle] Cannot publish pom for project ':' since it does not contain the Maven plugin install task and task ':artifactoryPublish' does not specify a custom pom path. #327
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
Comments
I am facing the same issue on spotless checks. |
Anyone found answer? |
same issue... |
bump the plugin to the latest version and add a publishing block, e.g.
|
This doesn't help for me! What Gradle version are you using? I tried with both 6.2 and 7.0 |
Using 7.0 Ensure:
|
I'm using Gradle 6.9. Plugin version 4.29.0. Single project.
It does appear to be publishing the pom (see below). Maybe the error is spurious?
|
Same issue even with Gradle-7.6.1 & Plugin version 4.31.4. Please, share update if anyone found any workaround to avoid a bunch of these error in build console logs? |
Here's the build.gradle I'm using to publish jars to artifactory with maven pom.xml, stripped down to the basics. Using gradle 7.4.1 You'll need to ensure all the relevant ENV are set to use.
|
Running any Gradle task triggers lots of
Cannot publish pom for project ':' since it does not contain the Maven plugin install task and task ':artifactoryPublish' does not specify a custom pom path.
messages.Example
build.gradle
to reproduce:Expected behavior:
publishToMavenLocal
would publish, to artifactory.So far it seems to be impossible to publish all artifacts and have all dependencies in the build-info without also having MEGABYTES of the warning above in the build logs (our actual builds have many more subprojects obviously)
The text was updated successfully, but these errors were encountered: