[GRADLE-2004] Fail upload on missing artifacts Created: 17/Dec/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 0


Hi guys,
I'm having a build that adds publish artifacts which are built by some Jar tasks created dynamically. I noticed that if I execute uploadArchives, without having run those Jar tasks, the Upload succeeds but does NOT upload the missing artifacts, although they get defined in the ivy descriptor.
The log contains the following 'DEBUG' messages:

6:39:01.646 [DEBUG] [org.gradle.api.internal.artifacts.ivyservice.IvyLoggingAdaper] missing artifact org.acme#foo;1.0.0!foo-profile.jar(profile):
[java] D:\workspace\acme\antBuild\profiles\foo-profile-1.0.0-sources.jar file does not exist

It seems more appropriate to fail the upload if some artifact is declared but not found, is there a way to do this?

I'm using gradle-1.0-milestone-6-20111114000013+0100.


Comment by Gradle Forums [ 17/Dec/11 ]

Hey Detelin!

It looks like a bug to me. I'll export it to jira. Is there a chance you could provide a sample project that demonstrates this behavior? BTW. Can you still reproduce this issue with released M6?

Comment by Adam Murdoch [ 03/Sep/13 ]

This is fixed in the new `ivy-publish` plugins, but not in the old `uploadArchives` task.

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:10:10 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.