You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is currently no way to make `swift test` in previous-version compatibility mode so as to test behaviour in every case – this is obviously useful for a library that might be included by another package that itself still builds using a compatibility mode.
The workaround is obviously to manipulate and rename package manifests, but that is less than desirable.
The text was updated successfully, but these errors were encountered:
Forgive my denseness, but I don't see what the solution was here.
I still can't figure out how to make the swift 5 tools run my test in 4.2 mode without juggling manifests. I really thought the following (or something equivalent) would become a possibility:
Additional Detail from JIRA
md5: 0bb0bfd7b3747290341cf21cd0e1619c
Issue Description:
If I have versioned package manifests such as
Package.swift // swift-tools-version:4.2
Package@swift-3.1.swift
Package@swift-4.swift
There is currently no way to make `swift test` in previous-version compatibility mode so as to test behaviour in every case – this is obviously useful for a library that might be included by another package that itself still builds using a compatibility mode.
The workaround is obviously to manipulate and rename package manifests, but that is less than desirable.
The text was updated successfully, but these errors were encountered: