Hello SwiftPM community,
Last week we landed a significant reworking of how SwiftPM generates Xcode project files (https://github.com/apple/swift-package-manager/pull/639). These changes are on `master` and have not yet shipped in any release.
In addition to addressing most of the reported bugs (though not all limitations) of the Xcode project generation feature in SwiftPM, it also makes future fixes and improvements easier by making the code layered and testable. There are further improvements that have landed on `master` since then, taking advantage of the cleaner layering.
We would like to pull these fixes into an upcoming Swift bug-fix release. In order to reduce the risk of undetected regressions, we'd like to ask anyone who uses the `swift package generate-xcodeproj` feature regularly to try it out on their packages using a snapshot of `master` (which can be downloaded from https://swift.org/download/#snapshots). There are instructions for how to use a downloaded toolchain further down on the same page (at https://swift.org/download/#using-downloads).
Xcode projects do not need to be built using the same toolchain that generated it, so once the project has been generated, you can use it with whatever toolchain you normally use for your code (for example the default toolchain in Xcode). Because the compiler in the downloaded snapshot is not a release build, it may be unsuitable for compiling your code; this is only a request to use it for the `swift package generate-xcodeproj` invocation itself.
We are particularly interested in any regressions in the project generation, but if there are new issues or issues that still aren't fixed, we'd very much appreciate if you'd take the time to file a JIRA at bugs.swift.org (using the `Package Manager` component).