Debian Codegraph @

doc/releasing-antlr.md

raw
1 # Cutting an ANTLR Release
2
3 ## Github
4
5 Create a pre-release or full release at github; [Example 4.5-rc-1](https://github.com/antlr/antlr4/releases/tag/4.5-rc-1).
6
7 ### Delete existing release tag
8
9 Wack any existing tag as mvn will create one and it fails if already there.
10
11 ```
12 $ git tag -d 4.9
13 $ git push origin :refs/tags/4.9
14 $ git push upstream :refs/tags/4.9
15 ```
16
17 ### Create release candidate tag
18
19 ```bash
20 $ git tag -a 4.9-rc1 -m 'heading towards 4.9'
21 $ git push origin 4.9-rc1
22 $ git push upstream 4.9-rc1
23 ```
24
25 ## Copy PHP runtime over
26
27 Bump version to 4.9 in `~/antlr/code/antlr-php-runtime/src/RuntimeMetaData.php` in separate repository and commit plus push.
28
29 ```
30 cd ~/antlr/code/antlr-php-runtime/src
31 ... vi RuntimeMetaData.php ...
32 git commit -a -m "Update PHP Runtime to latest version"
33 ```
34
35 them back over in the ANTLR repo:
36
37 ```
38 cd runtime
39 rm -rf PHP
40 mkdir PHP
41 cp ~/antlr/code/antlr-php-runtime/LICENSE PHP
42 cp ~/antlr/code/antlr-php-runtime/README.md PHP
43 cp ~/antlr/code/antlr-php-runtime/composer.json PHP
44 cp ~/antlr/code/antlr-php-runtime/phpcs.xml.dist PHP
45 cp ~/antlr/code/antlr-php-runtime/phpstan.neon.dist PHP
46 cp -r ~/antlr/code/antlr-php-runtime/src PHP
47 ```
48
49 ## Bump version
50
51 Edit the repository looking for 4.5 or whatever and update it. Bump version in the following files:
52
53 * runtime/Java/src/org/antlr/v4/runtime/RuntimeMetaData.java
54 * runtime/Python2/setup.py
55 * runtime/Python2/src/antlr4/Recognizer.py
56 * runtime/Python3/setup.py
57 * runtime/Python3/src/antlr4/Recognizer.py
58 * runtime/CSharp/src/Antlr4.csproj
59 * runtime/PHP/src/RuntimeMetaData.php
60 * runtime/JavaScript/package.json
61 * runtime/JavaScript/src/antlr4/Recognizer.js
62 * runtime/JavaScript/package-lock.json
63 * runtime/Cpp/VERSION
64 * runtime/Cpp/runtime/src/RuntimeMetaData.cpp
65 * runtime/Cpp/cmake/ExternalAntlr4Cpp.cmake
66 * runtime/Cpp/demo/generate.cmd
67 * runtime/Go/antlr/recognizer.go
68 * runtime/Swift/Antlr4/org/antlr/v4/runtime/RuntimeMetaData.swift
69 * runtime/Dart/lib/src/runtime_meta_data.dart
70 * runtime/Dart/pubspec.yaml
71 * runtime/Swift/Tests/Antlr4Tests/RuntimeMetaDataTests.swift
72 * runtime/Swift/Sources/Antlr4/RuntimeMetaData.swift
73 * runtime/CSharp/src/Tree/Xpath/XPathLexer.cs
74 * runtime/CSharp/src/README.md
75 * runtime/CSharp/src/Properties/AssemblyInfo.cs
76 * tool/src/org/antlr/v4/codegen/target/GoTarget.java
77 * tool/src/org/antlr/v4/codegen/target/CppTarget.java
78 * tool/src/org/antlr/v4/codegen/target/CSharpTarget.java
79 * tool/src/org/antlr/v4/codegen/target/JavaScriptTarget.java
80 * tool/src/org/antlr/v4/codegen/target/Python2Target.java
81 * tool/src/org/antlr/v4/codegen/target/Python3Target.java
82 * tool/src/org/antlr/v4/codegen/target/SwiftTarget.java
83 * tool/src/org/antlr/v4/codegen/target/PHPTarget.java
84 * tool/src/org/antlr/v4/codegen/Target.java
85 * tool/resources/org/antlr/v4/tool/templates/codegen/Swift/Swift.stg
86
87 Here is a simple script to display any line from the critical files with, say, `4.9` in it:
88
89 ```bash
90 mvn clean
91 rm -rf runtime/CSharp/src/bin
92 rm -rf runtime/CSharp/src/obj
93 rm -rf runtime/Cpp/runtime/build
94 rm -rf runtime/gen
95 rm -rf runtime/JavaScript/dist
96 find tool runtime -type f -exec grep -l '4\.9' {} \;
97 ```
98
99 Commit to repository.
100
101 ## Building
102
103 ugh. apparently you have to `mvn install` and then `mvn compile` or some such or subdir pom.xml's won't see the latest runtime build.
104
105 ## Maven Repository Settings
106
107 First, make sure you have maven set up to communicate with staging servers etc... Create file `~/.m2/settings.xml` with appropriate username/password for staging server and gpg.keyname/passphrase for signing. Make sure it has strict visibility privileges to just you. On unix, it looks like:
108
109 ```bash
110 beast:~/.m2 $ ls -l settings.xml
111 -rw------- 1 parrt staff 914 Jul 15 14:42 settings.xml
112 ```
113
114 Here is the file template
115
116 ```xml
117 <?xml version="1.0" encoding="UTF-8"?>
118 <!--
119 User-specific configuration for maven. Includes things that should not
120 be distributed with the pom.xml file, such as developer identity, along with
121 local settings, like proxy information.
122 -->
123 <settings>
124 <servers>
125 <server>
126 <id>sonatype-nexus-staging</id>
127 <username>sonatype-username</username>
128 <password>XXX</password>
129 </server>
130 <server>
131 <id>sonatype-nexus-snapshots</id>
132 <username>sonatype-username</username>
133 <password>XXX</password>
134 </server>
135 </servers>
136 <profiles>
137 <profile>
138 <activation>
139 <activeByDefault>false</activeByDefault>
140 </activation>
141 <properties>
142 <gpg.keyname>UUU</gpg.keyname>
143 <gpg.passphrase>XXX</gpg.passphrase>
144 </properties>
145 </profile>
146 </profiles>
147 </settings>
148 ```
149
150 ## Maven deploy snapshot
151
152 The goal is to get a snapshot, such as `4.9-SNAPSHOT`, to the staging server: [antlr4 tool](https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4) and [antlr4 java runtime](https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4-runtime).
153
154 Do this:
155
156 ```bash
157 $ mvn install -DskipTests # seems required to get the jar files visible to maven
158 $ mvn deploy -DskipTests
159 ...
160 [INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ antlr4-tool-testsuite ---
161 Downloading: https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4-tool-testsuite/4.9-SNAPSHOT/maven-metadata.xml
162 Uploading: https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4-tool-testsuite/4.9-SNAPSHOT/antlr4-tool-testsuite-4.9-20161211.173752-1.jar
163 Uploaded: https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4-tool-testsuite/4.9-SNAPSHOT/antlr4-tool-testsuite-4.9-20161211.173752-1.jar (3 KB at 3.4 KB/sec)
164 Uploading: https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4-tool-testsuite/4.9-SNAPSHOT/antlr4-tool-testsuite-4.9-20161211.173752-1.pom
165 Uploaded: https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4-tool-testsuite/4.9-SNAPSHOT/antlr4-tool-testsuite-4.9-20161211.173752-1.pom (3 KB at 6.5 KB/sec)
166 Downloading: https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4-tool-testsuite/maven-metadata.xml
167 Downloaded: https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4-tool-testsuite/maven-metadata.xml (371 B at 1.4 KB/sec)
168 Uploading: https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4-tool-testsuite/4.9-SNAPSHOT/maven-metadata.xml
169 Uploaded: https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4-tool-testsuite/4.9-SNAPSHOT/maven-metadata.xml (774 B at 1.8 KB/sec)
170 Uploading: https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4-tool-testsuite/maven-metadata.xml
171 Uploaded: https://oss.sonatype.org/content/repositories/snapshots/org/antlr/antlr4-tool-testsuite/maven-metadata.xml (388 B at 0.9 KB/sec)
172 [INFO] ------------------------------------------------------------------------
173 [INFO] Reactor Summary:
174 [INFO]
175 [INFO] ANTLR 4 ............................................ SUCCESS [ 4.073 s]
176 [INFO] ANTLR 4 Runtime .................................... SUCCESS [ 13.828 s]
177 [INFO] ANTLR 4 Tool ....................................... SUCCESS [ 14.032 s]
178 [INFO] ANTLR 4 Maven plugin ............................... SUCCESS [ 6.547 s]
179 [INFO] ANTLR 4 Runtime Test Annotations ................... SUCCESS [ 2.519 s]
180 [INFO] ANTLR 4 Runtime Test Processors .................... SUCCESS [ 2.385 s]
181 [INFO] ANTLR 4 Runtime Tests (2nd generation) ............. SUCCESS [ 15.276 s]
182 [INFO] ANTLR 4 Tool Tests ................................. SUCCESS [ 2.233 s]
183 [INFO] ------------------------------------------------------------------------
184 [INFO] BUILD SUCCESS
185 [INFO] ------------------------------------------------------------------------
186 [INFO] Total time: 01:01 min
187 [INFO] Finished at: 2016-12-11T09:37:54-08:00
188 [INFO] Final Memory: 44M/470M
189 [INFO] ------------------------------------------------------------------------
190 ```
191
192 ## Maven release
193
194 The maven deploy lifecycle phased deploys the artifacts and the poms for the ANTLR project to the [sonatype remote staging server](https://oss.sonatype.org/content/repositories/snapshots/).
195
196 ```bash
197 export JAVA_HOME=`/usr/libexec/java_home -v 1.7`; mvn deploy -DskipTests
198 ```
199
200 With JDK 1.7 (not 6 or 8), do this:
201
202 ```bash
203 export JAVA_HOME=`/usr/libexec/java_home -v 1.7`; mvn release:prepare -Darguments="-DskipTests"
204 ```
205
206 Hm...per https://github.com/keybase/keybase-issues/issues/1712 we need this to make gpg work:
207
208 ```bash
209 export GPG_TTY=$(tty)
210 ```
211
212 Side note to set jdk 1.7 on os x:
213
214 ```bash
215 alias java="`/usr/libexec/java_home -v 1.7`/bin/java"
216 alias javac="`/usr/libexec/java_home -v 1.7`/bin/javac"
217 alias javadoc="`/usr/libexec/java_home -v 1.7`/bin/javadoc"
218 alias jar="`/usr/libexec/java_home -v 1.7`/bin/jar"
219 export JAVA_HOME=`/usr/libexec/java_home -v 1.7`
220 ```
221
222 But I think just this on front of mvn works:
223
224 ```
225 export JAVA_HOME=`/usr/libexec/java_home -v 1.7`; mvn ...
226 ```
227
228 You should see 0x33 in generated .class files after 0xCAFEBABE; see [Java SE 7 = 51 (0x33 hex)](https://en.wikipedia.org/wiki/Java_class_file):
229
230 ```bash
231 beast:/tmp/org/antlr/v4 $ od -h Tool.class |head -1
232 0000000 feca beba 0000 3300 fa04 0207 0ab8 0100
233 ```
234
235 It will start out by asking you the version number:
236
237 ```
238 ...
239 What is the release version for "ANTLR 4"? (org.antlr:antlr4-master) 4.9: : 4.9
240 What is the release version for "ANTLR 4 Runtime"? (org.antlr:antlr4-runtime) 4.9: :
241 What is the release version for "ANTLR 4 Tool"? (org.antlr:antlr4) 4.9: :
242 What is the release version for "ANTLR 4 Maven plugin"? (org.antlr:antlr4-maven-plugin) 4.9: :
243 What is the release version for "ANTLR 4 Runtime Test Generator"? (org.antlr:antlr4-runtime-testsuite) 4.9: :
244 What is the release version for "ANTLR 4 Tool Tests"? (org.antlr:antlr4-tool-testsuite) 4.9: :
245 What is SCM release tag or label for "ANTLR 4"? (org.antlr:antlr4-master) antlr4-master-4.9: : 4.9
246 What is the new development version for "ANTLR 4"? (org.antlr:antlr4-master) 4.9.1-SNAPSHOT:
247 ...
248 ```
249
250 Maven will go through your pom.xml files to update versions from 4.9-SNAPSHOT to 4.9 for release and then to 4.9.1-SNAPSHOT after release, which is done with:
251
252 ```bash
253 mvn release:perform -Darguments="-DskipTests"
254 ```
255
256 Maven will use git to push pom.xml changes.
257
258 Now, go here:
259
260 &nbsp;&nbsp;&nbsp;&nbsp;[https://oss.sonatype.org/#welcome](https://oss.sonatype.org/#welcome)
261
262 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:
263
264 &nbsp;&nbsp;&nbsp;&nbsp;[https://oss.sonatype.org/service/local/repositories/releases/content/org/antlr/antlr4-runtime/4.9-1/antlr4-runtime-4.9-1.jar](https://oss.sonatype.org/service/local/repositories/releases/content/org/antlr/antlr4-runtime/4.9-1/antlr4-runtime-4.9-1.jar)
265
266 All releases should be here: https://repo1.maven.org/maven2/org/antlr/antlr4-runtime/
267
268 Copy the jars to antlr.org site and update download/index.html
269
270 ```bash
271 cp ~/.m2/repository/org/antlr/antlr4-runtime/4.9/antlr4-runtime-4.9.jar ~/antlr/sites/website-antlr4/download/antlr-runtime-4.9.jar
272 cp ~/.m2/repository/org/antlr/antlr4/4.9/antlr4-4.9-complete.jar ~/antlr/sites/website-antlr4/download/antlr-4.9-complete.jar
273 cd ~/antlr/sites/website-antlr4/download
274 git add antlr-4.9-complete.jar
275 git add antlr-runtime-4.9.jar
276 ```
277
278 Update on site:
279
280 * download.html
281 * index.html
282 * api/index.html
283 * download/index.html
284 * scripts/topnav.js
285
286 ```
287 git commit -a -m 'add 4.9 jars'
288 git push origin gh-pages
289 ```
290
291 ## Deploying Targets
292
293 ### JavaScript
294
295 ```bash
296 cd runtime/JavaScript
297 # git add, commit, push
298 ```
299
300 **Push to npm**
301
302 ```bash
303 cd runtime/JavaScript
304 npm update
305 npm install
306 npm run build
307 npm login
308 npm publish # don't put antlr4 on there or it will try to push the old version for some reason
309 ```
310
311 Move (and zip) target to website:
312
313 ```bash
314 cd src
315 zip -r ~/antlr/sites/website-antlr4/download/antlr-javascript-runtime-4.9.zip .
316 ```
317
318 ### CSharp
319
320 Now we have [appveyor create artifact](https://ci.appveyor.com/project/parrt/antlr4/build/artifacts). Go to [nuget](https://www.nuget.org/packages/manage/upload) to upload the `.nupkg`.
321
322 ### Publishing to Nuget from Windows
323
324 **Install the pre-requisites**
325
326 Of course you need Mono and `nuget` to be installed. On mac:
327
328 - .NET build tools - can be loaded from [here](https://www.visualstudio.com/downloads/) (I need dotnet 5 and 3.1 versions)
329 - nuget - download [nuget.exe](https://www.nuget.org/downloads)
330 - dotnet - follow [the instructions here](https://www.microsoft.com/net/core)
331
332 From @kvanTTT: Install `dotnet` on any platform (see https://dotnet.microsoft.com/download) and run the following command on any OS (Win, Linux, macOS):
333
334 * building: `dotnet build runtime/CSharp/src/Antlr4.csproj -c Release`
335 Output `.dll` will be in `runtime/CSharp/src/bin/Release/netstandard2.0` or in `runtime/CSharp/src/bin/Release/netstandard2.1`
336 * packing: `dotnet pack runtime/CSharp/src/Antlr4.csproj -c Release`
337 Output `.nupkg` will be in `runtime/CSharp/src/bin/Release/Antlr4.Runtime.Standard.4.9.1.nupkg`
338
339 Alternatively, you can install Visual Studio 2017 and make sure to check boxes with .NET Core SDK.
340
341 You also need to enable .NET Framework 3.5 support in Windows "Programs and Features".
342
343 If everything is ok, the following command will restore nuget packages, build Antlr for .NET Standard and .NET 3.5 and create nuget package:
344
345 ```PS
346 msbuild /target:restore /target:rebuild /target:pack /property:Configuration=Release .\Antlr4.dotnet.sln /verbosity:minimal
347 ```
348
349 This should display something like this:
350
351 **Creating and packaging the assembly**
352
353 ```
354 Microsoft (R) Build Engine version 15.4.8.50001 for .NET Framework
355 Copyright (C) Microsoft Corporation. All rights reserved.
356
357 Restoring packages for C:\Code\antlr4-fork\runtime\CSharp\runtime\CSharp\Antlr4.Runtime\Antlr4.Runtime.dotnet.csproj...
358 Generating MSBuild file C:\Code\antlr4-fork\runtime\CSharp\runtime\CSharp\Antlr4.Runtime\obj\Antlr4.Runtime.dotnet.csproj.nuget.g.props.
359 Generating MSBuild file C:\Code\antlr4-fork\runtime\CSharp\runtime\CSharp\Antlr4.Runtime\obj\Antlr4.Runtime.dotnet.csproj.nuget.g.targets.
360 Restore completed in 427.62 ms for C:\Code\antlr4-fork\runtime\CSharp\runtime\CSharp\Antlr4.Runtime\Antlr4.Runtime.dotnet.csproj.
361 Antlr4.Runtime.dotnet -> C:\Code\antlr4-fork\runtime\CSharp\runtime\CSharp\Antlr4.Runtime\lib\Release\netstandard1.3\Antlr4.Runtime.Standard.dll
362 Antlr4.Runtime.dotnet -> C:\Code\antlr4-fork\runtime\CSharp\runtime\CSharp\Antlr4.Runtime\lib\Release\net35\Antlr4.Runtime.Standard.dll
363 Successfully created package 'C:\Code\antlr4-fork\runtime\CSharp\runtime\CSharp\Antlr4.Runtime\lib\Release\Antlr4.Runtime.Standard.4.9.2.nupkg'.
364 ```
365
366 **Publishing to NuGet**
367
368 You need to be a NuGet owner for "ANTLR 4 Standard Runtime"
369 As a registered NuGet user, you can then manually upload the package here: [https://www.nuget.org/packages/manage/upload](https://www.nuget.org/packages/manage/upload)
370
371 Alternately, you can publish from the cmd line. You need to get your NuGet key from [https://www.nuget.org/account#](https://www.nuget.org/account#) and then from the cmd line, you can then type:
372
373 ```cmd
374 nuget push Antlr4.Runtime.Standard.<version>.nupkg <your-key> -Source https://www.nuget.org/api/v2/package
375 ```
376
377 Nuget packages are also accessible as artifacts of [AppVeyor builds](https://ci.appveyor.com/project/parrt/antlr4/build/artifacts).
378
379 ### Python
380
381 The Python targets get deployed with `setup.py`. First, set up `~/.pypirc` with tight privileges:
382
383 ```bash
384 beast:~ $ ls -l ~/.pypirc
385 -rw------- 1 parrt staff 267 Jul 15 17:02 /Users/parrt/.pypirc
386 ```
387
388 ```
389 [distutils] # this tells distutils what package indexes you can push to
390 index-servers =
391 pypi
392 pypitest
393
394 [pypi]
395 username: parrt
396 password: xxx
397
398 [pypitest]
399 username: parrt
400 password: xxx
401 ```
402
403 Then run the usual python set up stuff:
404
405 ```bash
406 cd ~/antlr/code/antlr4/runtime/Python2
407 # assume you have ~/.pypirc set up
408 python2 setup.py sdist upload
409 ```
410
411 and do again for Python 3 target
412
413 ```bash
414 cd ~/antlr/code/antlr4/runtime/Python3
415 # assume you have ~/.pypirc set up
416 python3 setup.py sdist upload
417 ```
418
419 There are links to the artifacts in [download.html](http://www.antlr.org/download.html) already.
420
421 ### C++
422
423 The C++ target is the most complex one, because it addresses multiple platforms, which require individual handling. We have 4 scenarios to cover:
424
425 * **Windows**: static and dynamic libraries for the VC++ runtime 2017 or 2019 (corresponding to Visual Studio 2017 or 2019) + header files. All that in 32 and 64bit, debug + release.
426 * **MacOS**: static and dynamic release libraries + header files.
427 * **iOS**: no prebuilt binaries, but just a zip of the source, including the XCode project to build everything from source.
428 * **Linux**: no prebuilt binaries, but just a zip of the source code, including the cmake file to build everything from source there.
429
430 In theory we could also create a library for iOS, but that requires to sign it, which depends on an active iOS developer account. So we leave this up to the ANTLR user to build the iOS lib, like we do for Linux builds.
431
432 For each platform there's a deployment script which generates zip archives and copies them to the target folder. The Windows deployment script must be run on a machine with VS 2013 + VS 2015 installed. The Mac script must be run on a machine with XCode 7+ installed. The source script can be executed on any Linux or Mac box.
433
434 On a Mac (with XCode 7+ installed):
435
436 ```bash
437 cd runtime/Cpp
438 ./deploy-macos.sh
439 cp antlr4-cpp-runtime-macos.zip ~/antlr/sites/website-antlr4/download/antlr4-cpp-runtime-4.9-macos.zip
440 ```
441
442 On any Mac or Linux machine:
443
444 ```bash
445 cd runtime/Cpp
446 ./deploy-source.sh
447 cp antlr4-cpp-runtime-source.zip ~/antlr/sites/website-antlr4/download/antlr4-cpp-runtime-4.9-source.zip
448 ```
449
450 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).
451
452 ```bash
453 cd runtime/Cpp
454 deploy-windows.cmd Community
455 cp antlr4-cpp-runtime-vs2019.zip ~/antlr/sites/website-antlr4/download/antlr4-cpp-runtime-4.9-vs2019.zip
456 ```
457
458 Move target to website (**_rename to a specific ANTLR version first if needed_**):
459
460 ```bash
461 pushd ~/antlr/sites/website-antlr4/download
462 # vi index.html
463 git add antlr4-cpp-runtime-4.9-macos.zip
464 git add antlr4-cpp-runtime-4.9-windows.zip
465 git add antlr4-cpp-runtime-4.9-source.zip
466 git commit -a -m 'update C++ runtime'
467 git push origin gh-pages
468 popd
469 ```
470
471 ### Dart
472
473 Install Dart SDK from https://dart.dev/get-dart
474
475 Push to pub.dev
476
477 ```bash
478 cd runtime/Dart
479 pub publish
480 ```
481
482 It will warn that no change log found for the new version.
483 If there are changes relevant to dart in this release, edit [CHANGELOG.md](https://github.com/antlr/antlr4/blob/master/runtime/Dart/CHANGELOG.md) to describe the changes.
484 Otherwise enter `N` to ignore the warning.
485
486 ## Update javadoc for runtime and tool
487
488 First, gen javadoc:
489
490 ```bash
491 $ cd antlr4
492 $ mvn -DskipTests javadoc:jar install
493 ```
494
495 Then copy to website:
496
497 ```bash
498 cd ~/antlr/sites/website-antlr4/api
499 git checkout gh-pages
500 git pull origin gh-pages
501 cd Java
502 jar xvf ~/.m2/repository/org/antlr/antlr4-runtime/4.9/antlr4-runtime-4.9-javadoc.jar
503 cd ../JavaTool
504 jar xvf ~/.m2/repository/org/antlr/antlr4/4.9/antlr4-4.9-javadoc.jar
505 git commit -a -m 'freshen api doc'
506 git push origin gh-pages
507 ```
508
509 ## Update Intellij plug-in
510
511 Rebuild antlr plugin with new antlr jar.