This package has a release tagged as 0.2.0, but that release is not usable (and neither is 0.1.0) because the library relies on swift-java via its main branch instead of a tagged release. SwiftPM rejects such scenarios.
I believe that when 0.2.0 was tagged, swift-java didn't have a recent enough release, but as of two weeks ago swift-java tagged its own 0.2.0 release. I believe that this package should be able to depend on swift-java 0.2.0. Then if you tag a new release of this package, people will be able to depend on it by tag instead of just by commit or branch requirements.
https://github.com/PureSwift/Kotlin also has the same issue (because it relies on both swift-java and this package via unstable branch requirements).
Once the unstable requirements are resolved in this package and the PureSwift/Kotlin package, I believe that you should be able to update all of PureSwift/Android's dependency declarations to use stable versions, and then if you tag a new release of PureSwift/Android consumers (such as SwiftCrossUI) can depend on PureSwift/Android via a stable version, and can themselves vend usable stable versions.
This package has a release tagged as
0.2.0, but that release is not usable (and neither is0.1.0) because the library relies on swift-java via itsmainbranch instead of a tagged release. SwiftPM rejects such scenarios.I believe that when 0.2.0 was tagged, swift-java didn't have a recent enough release, but as of two weeks ago swift-java tagged its own 0.2.0 release. I believe that this package should be able to depend on swift-java 0.2.0. Then if you tag a new release of this package, people will be able to depend on it by tag instead of just by commit or branch requirements.
https://github.com/PureSwift/Kotlin also has the same issue (because it relies on both swift-java and this package via unstable branch requirements).
Once the unstable requirements are resolved in this package and the PureSwift/Kotlin package, I believe that you should be able to update all of PureSwift/Android's dependency declarations to use stable versions, and then if you tag a new release of PureSwift/Android consumers (such as SwiftCrossUI) can depend on PureSwift/Android via a stable version, and can themselves vend usable stable versions.