[GRADLE-3458] Incorrect artifact file parsed as POM, resulting in "Content is not allowed in prolog" Created: 24/May/16  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Daz DeBoer Assignee: Unassigned
Resolution: Won't Fix Votes: 1

Attachments: File artifact-at-repository.bin    
Issue Links:
Related to GRADLE-3015 Incorrect artifact file resolved from... Resolved


This is very likely the same as GRADLE-3015, where the incorrect artifact file is retrieved from the cache. In this case, the requested artifact is a POM file and the returned artifact a Jar file, resulting in "Content is not allowed in prolog" when attempting to parse the POM.

The offending cache file is `artifact-at-repository.bin`. This cache was discovered on one of the Gradle CI servers, and has been attached to this issue. On OSX this file is detected as being corrupt, which permits Gradle to clean it up and continue. On Linux however, this cache file produces the incorrect artifact file when a particular Parent POM is requested, resulting in incorrect behaviour.

Output for this failure condition on OSX and Linux can be viewed here:

To reproduce this issue, clone the Gradle repository for the 2.14-rc-2 release, and replace the cache file `caches/modules-2/metadata-2.16/artifact-at-repository.bin` with the attached 'artifact-at-repository.bin' file.

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