Commit 0d39a0e
committed
Set version to 0.0.0-SNAPSHOT.
We released 0.2.0, so it's well past time for us to move past
0.1.0-SNAPSHOT.
The next obvious possibility would be 0.3.0-SNAPSHOT (or, if we're
optimistic, 1.0.0-SNAPSHOT). However, using _any_ version number
complicates matters for anyone who wants to build this repo and use it.
Notably, our own
https://github.com/jspecify/nullness-checker-for-checker-framework
suggests using jspecify-0.1.0-SNAPSHOT.jar on the classpath. (And that
same project has had mild difficulties with the Checker Framework test
jar, which has a name like framework-test-3.11.1-SNAPSHOT.jar:
jspecify/jspecify-reference-checker@edd8a76#diff-49a96e7eea8a94af862798a45174e6ac43eb4f8b4bd40759b5da63ba31ec3ef7)
To avoid this in some Google projects, we've used the version "number"
of "HEAD-SNAPSHOT":
https://github.com/google/truth/blob/3c580fc7971d85ba3b0b642310b29f101a7451c7/pom.xml#L14
However, that causes problems with the Java module system: Even though
[`ModuleDescriptor.Version`](https://docs.oracle.com/en/java/javase/16/docs/api/java.base/java/lang/module/ModuleDescriptor.Version.html)
suggests that "HEAD-SNAPSHOT" should be valid, the implementation
rejects it.
Other people have this problem:
- https://issues.apache.org/jira/browse/MCOMPILER-446
- AlmasB/FXGL#1091 (comment)
- devonfw/ide#539 (comment)
I liked the last link's suggestion of a "version 0," so here we are :)1 parent 6c3f286 commit 0d39a0e
1 file changed
+1
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | | - | |
| 2 | + | |
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
| |||
0 commit comments