[GRADLE-2907] "Failed to validate POM for project" in uploading artifacts task Created: 30/Sep/13  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 4


 Description   

Hi all,

We have a big problem with uploading task. Uploading fails with generic "Failed to validate POM for project" and no more information.
The build always fails when uploading the jar for war subprojects, both using the original publishing mechanism and the new maven-publish plugin.

We try with gradle version 1.5, 1.6 and 1.7, but the error is always the same. Here a [gist with the stack trace]([1]https://gist.github.com/davidecavestr...).

Follows an excerpt of our last attempt of configuring the upload for subprojects

subprojects {subprj->
configurations {
batchConfig
}
artifacts{
batchConfig jar
}
uploadBatchConfig{
repositories {
mavenDeployer {
repository(url: "file:///tmp/m2/")
}
}
}
rootProject.uploadBatchConfig.dependsOn subprj.uploadBatchConfig
}

It could be our fault (the multiproject build is quite complex) but without further details on the validation failure cause, we have no chances to fix it.
----------------------------------------------------------------------------------------
[1] https://gist.github.com/davidecavestro/6624920

 Comments   
Comment by Gradle Forums [ 30/Sep/13 ]

Have you investigated the POM mentioned in the exception message?

Comment by Gradle Forums [ 30/Sep/13 ]

Yes I have. For me the POM appears correct.

I uploaded it in a [gist]([1]https://gist.github.com/andreaschiona...)
----------------------------------------------------------------------------------------
[1] https://gist.github.com/andreaschiona/6763957

Comment by Gradle Forums [ 30/Sep/13 ]

First thing I'd do is to verify this POM against its schema.

Comment by Gradle Forums [ 30/Sep/13 ]

I've already checked this thing and it successfully passes the validation

Comment by Gradle Forums [ 30/Sep/13 ]

Looking at the code, I don't understand why the root cause is missing from the output. Can you show the stack trace when running with `--full-stacktrace`?

Comment by Gradle Forums [ 30/Sep/13 ]

[Here]([1]https://gist.github.com/andreaschiona...) you can found the stack trace when running with --full-stacktrace.

Unfortunally gradle don't show the "real" problem!
----------------------------------------------------------------------------------------
[1] https://gist.github.com/andreaschiona/6766000

Comment by Gradle Forums [ 30/Sep/13 ]

As you can see from the stack trace, Gradle is calling into Maven here, and apparently the only thing it gets back is this exception. I'll see if I can find something in the Maven sources.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:34:40 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.