[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
This is very likely the same as
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:
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.