-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Problem: d218094 set the version to 0.7.0-SNAPSHOT, but that change failed to produce the intended effect detailed in the commit comment. Setting the version to a value like 0.7.0-SNAPSHOT works fine when publishing artifacts to a local ~/.m2 repository, but JitPack has no awareness of version metadata within pom files, and can only retreive artifacts based on Git metadata, namely tags, branch names and commit hashes. This means it is impossible to resolve artifacts from JitPack with a GAV like `io.bisq.exchange:core:0.7.0-SNAPSHOT` unless there is a branch named `0.7.0`. This is why the pull request at bisq-network/bisq-seednode#1 failed. Solution: JitPack supports the semantics of Maven-style `-SNAPSHOT` versioning, and as a special case, allows for versions to be named literally `-SNAPSHOT` with no preceding version string [1,2]. This commit sets all Maven versions to `-SNAPSHOT`, achieving the original effect intended by d218094. Now downstream components (like bisq-seednode) can resolve dependencies seamlessly from JitPack or a local ~/.m2 repo with a GAV like `io.bisq.exchange:core:-SNAPSHOT`. This is a slightly unconventional arrangement, but should actually result in fewer updates to pom files over time as there may in fact be no reason to ever change this version string so long as we continue using JitPack and avoid publication to Maven Central / JCenter or similar. [1]: https://jitpack.io/docs/#building-with-jitpack [2]: jitpack/jitpack.io#351 See #1440
- Loading branch information
Showing
8 changed files
with
8 additions
and
8 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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