Closed clackary closed 5 years ago
I think we should add diagnostics in SwiftPM explaining that we don't support v3 manifest anymore.
@aciidb0mb3r Ah, thanks for the context. If it breaks this many of our source compat projects, it's bound to be pretty common, so I agree about adding diagnostics.
Thanks Clack. I finally got around to resolve this issue for my projects, I've submitted these PRs: https://github.com/apple/swift-source-compat-suite/pull/269 and https://github.com/apple/swift-source-compat-suite/pull/270.
Additional Detail from JIRA
| | | |------------------|-----------------| |Votes | 0 | |Component/s | Project Infrastructure | |Labels | Bug | |Assignee | @clackary | |Priority | Medium | md5: 903da7e17885a3bc1db10df11a78e3edrelates to:
Issue Description:
Failure logs:
https://ci.swift.org/view/Source%20Compatibility/job/swift-master-source-compat-suite/2113/artifact/swift-source-compat-suite/
Each contains the error message: error: manifest parse error(s)