Repository navigation
Resolve POM edges from the project's classpath closure - #221
Merged
Merged
Conversation
update and publish read projectDependencies for every project, so a ++ session failed on a sibling it never touches. Read the classpath closure, and refuse a resolved module that names more than one project.
The cache epoch is the hash of the ship row, so it moved when the line opened.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #220.
updateandpublishcollected POM edges withinAnyProject, so they evaluatedprojectDependenciesfor every project.++only switches projects whosecrossScalaVersionscontains that version, and sbt then refuses a Scala mismatch on a sibling the command never touches.zipxPomExclusionsnow readszipxPomEdgesfor the classpath closure (inDependencies). Two projects that resolve as the same module areDuplicateModuleinstead of a last-wins map.The exclusion rules are unchanged. Docs state the closure on "What a consumer resolves", and the
cmdpage states what++switches.plugin/scripted zipx/scala-switchruns++2.13.16thenlegacy/updateandlegacy/publishLocal, then++3.9.0then the same forapp, and checks each POM excludes only its ownmodelsartifact.zipx/pom-exclusionsstill passes.sbt "scalafmtAll; cleanFull; testFull"passed (122 tasks).