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
Copy file name to clipboardexpand all lines: doc/releasing-antlr.md
+46-46
Original file line number
Diff line number
Diff line change
@@ -25,21 +25,21 @@ Make sure this feature is turned on for the `antlr4` repo upon release.
25
25
Wack any existing tag as mvn will create one and it fails if already there.
26
26
27
27
```
28
-
$ git tag -d 4.13.0
29
-
$ git push origin :refs/tags/4.13.0
30
-
$ git push upstream :refs/tags/4.13.0
28
+
$ git tag -d 4.13.1
29
+
$ git push origin :refs/tags/4.13.1
30
+
$ git push upstream :refs/tags/4.13.1
31
31
```
32
32
33
33
### Go release tags
34
34
35
35
*I don't think this is necessary anymore as we have moved it release branch to https://github.com/antlr4-go/antlr*
36
36
37
-
It seems that [Go needs a `v` in the release git tag](https://go.dev/ref/mod#glos-version) so make sure that we double up with 4.13.0 and v4.13.0.
37
+
It seems that [Go needs a `v` in the release git tag](https://go.dev/ref/mod#glos-version) so make sure that we double up with 4.13.1 and v4.13.1.
38
38
39
39
```
40
-
$ git tag -a runtime/Go/antlr/v4/v4.13.0 -m "Go runtime module only"
41
-
$ git push upstream runtime/Go/antlr/v4/v4.13.0
42
-
$ git push origin runtime/Go/antlr/v4/v4.13.0
40
+
$ git tag -a runtime/Go/antlr/v4/v4.13.1 -m "Go runtime module only"
41
+
$ git push upstream runtime/Go/antlr/v4/v4.13.1
42
+
$ git push origin runtime/Go/antlr/v4/v4.13.1
43
43
```
44
44
45
45
@@ -77,7 +77,7 @@ Commit to repository.
77
77
78
78
### PHP runtime
79
79
80
-
We only have to copy the PHP runtime into the ANTLR repository to run the unittests. But, we still need to bump the version to 4.13.0 in `~/antlr/code/antlr-php-runtime/src/RuntimeMetaData.php` in the separate repository, commit, and push.
80
+
We only have to copy the PHP runtime into the ANTLR repository to run the unittests. But, we still need to bump the version to 4.13.1 in `~/antlr/code/antlr-php-runtime/src/RuntimeMetaData.php` in the separate repository, commit, and push.
81
81
82
82
```
83
83
cd ~/antlr/code/antlr-php-runtime/src
@@ -94,19 +94,19 @@ git push origin master
94
94
95
95
## Build XPath parsers
96
96
97
-
This section addresses a [circular dependency regarding XPath](https://github.com/antlr/antlr4/issues/3600). In the java target I avoided a circular dependency (gen 4.13.0 parser for XPath using 4.13.0 which needs it to build) by hand building the parser: runtime/Java/src/org/antlr/v4/runtime/tree/xpath/XPath.java. Probably we won't have to rerun this for the patch releases, just major ones that alter the ATN serialization.
97
+
This section addresses a [circular dependency regarding XPath](https://github.com/antlr/antlr4/issues/3600). In the java target I avoided a circular dependency (gen 4.13.1 parser for XPath using 4.13.1 which needs it to build) by hand building the parser: runtime/Java/src/org/antlr/v4/runtime/tree/xpath/XPath.java. Probably we won't have to rerun this for the patch releases, just major ones that alter the ATN serialization.
The goal is to get a snapshot, such as `4.13.0-SNAPSHOT`, to the staging server: [antlr4 tool](https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4/4.13.0-SNAPSHOT/) and [antlr4 java runtime](https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4-runtime/4.13.0-SNAPSHOT/).
159
+
The goal is to get a snapshot, such as `4.13.1-SNAPSHOT`, to the staging server: [antlr4 tool](https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4/4.13.1-SNAPSHOT/) and [antlr4 java runtime](https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4-runtime/4.13.1-SNAPSHOT/).
160
160
161
161
Do this:
162
162
@@ -227,18 +227,18 @@ It will start out by asking you the version number:
227
227
228
228
```
229
229
...
230
-
What is the release version for "ANTLR 4"? (org.antlr:antlr4-master) 4.13.0: : 4.13.0
231
-
What is the release version for "ANTLR 4 Runtime"? (org.antlr:antlr4-runtime) 4.13.0: :
232
-
What is the release version for "ANTLR 4 Tool"? (org.antlr:antlr4) 4.13.0: :
233
-
What is the release version for "ANTLR 4 Maven plugin"? (org.antlr:antlr4-maven-plugin) 4.13.0: :
234
-
What is the release version for "ANTLR 4 Runtime Test Generator"? (org.antlr:antlr4-runtime-testsuite) 4.13.0: :
235
-
What is the release version for "ANTLR 4 Tool Tests"? (org.antlr:antlr4-tool-testsuite) 4.13.0: :
236
-
What is SCM release tag or label for "ANTLR 4"? (org.antlr:antlr4-master) antlr4-master-4.13.0: : 4.13.0
237
-
What is the new development version for "ANTLR 4"? (org.antlr:antlr4-master) 4.13.1-SNAPSHOT:
230
+
What is the release version for "ANTLR 4"? (org.antlr:antlr4-master) 4.13.1: : 4.13.1
231
+
What is the release version for "ANTLR 4 Runtime"? (org.antlr:antlr4-runtime) 4.13.1: :
232
+
What is the release version for "ANTLR 4 Tool"? (org.antlr:antlr4) 4.13.1: :
233
+
What is the release version for "ANTLR 4 Maven plugin"? (org.antlr:antlr4-maven-plugin) 4.13.1: :
234
+
What is the release version for "ANTLR 4 Runtime Test Generator"? (org.antlr:antlr4-runtime-testsuite) 4.13.1: :
235
+
What is the release version for "ANTLR 4 Tool Tests"? (org.antlr:antlr4-tool-testsuite) 4.13.1: :
236
+
What is SCM release tag or label for "ANTLR 4"? (org.antlr:antlr4-master) antlr4-master-4.13.1: : 4.13.1
237
+
What is the new development version for "ANTLR 4"? (org.antlr:antlr4-master) 4.13.2-SNAPSHOT:
238
238
...
239
239
```
240
240
241
-
Maven will go through your pom.xml files to update versions from 4.13.0-SNAPSHOT to 4.13.0 for release and then to 4.13.1-SNAPSHOT after release, which is done with:
241
+
Maven will go through your pom.xml files to update versions from 4.13.1-SNAPSHOT to 4.13.1 for release and then to 4.13.2-SNAPSHOT after release, which is done with:
242
242
243
243
```bash
244
244
mvn release:perform -Darguments="-DskipTests"
@@ -252,7 +252,7 @@ Now, go here:
252
252
253
253
and on the left click "Staging Repositories". You click the staging repo and close it, then you refresh, click it and release it. It's done when you see it here:
On a Windows machine the build scripts checks if VS 2017 and/or VS 2019 are installed and builds binaries for each, if found. This script requires 7z to be installed (http://7-zip.org then do `set PATH=%PATH%;C:\Program Files\7-Zip\` from DOS not powershell).
0 commit comments