Lines Matching full:snapshot
113 (however the build may be able to locate this in the ANTLR snapshot or
172 [INFO] Building jar: /home/jimi/antlrsrc/code/antlr/main/target/antlr-master-3.4-SNAPSHOT-completejar.jar
179 java -jar ~/antlrsrc/code/antlr/main/target/antlr-master-3.4-SNAPSHOT-completejar.jar $*
186 version number. They should always contain a.b.c-SNAPSHOT
187 (e.g. 3.1.3-SNAPSHOT). Only release branches should have their pom
204 perforce, then modify the <version>a.b.c-SNAPSHOT</version> in the
230 3.1.4-SNAPSHOT, we need to change the antlr3-maven-plugin pom.xml and
241 deploy to the ANTLR repositories (snapshot or release) you must have
278 Note that so long as the artifacts are versioned with a.b.c-SNAPSHOT
279 then deployment will always be to the development snapshot
293 of ANTLR is 3.1.3-SNAPSHOT. This means that it will probably (but not
295 version will bump to 3.1.4-SNAPSHOT.
309 as an older snapshot (this is not super important, but procedure is
316 3.1.3-SNAPSHOT to 3.1.4-SNAPSHOT.
319 directory and change the version from 3.1.3-SNAPSHOT to
320 3.1.4-SNAPSHOT. Do the same for the pom.xml in the
333 [INFO] Parent is org.antlr:antlr-master:3.1.4-SNAPSHOT
335 [INFO] Parent is org.antlr:antlr-master:3.1.4-SNAPSHOT
337 [INFO] Parent is org.antlr:antlr-master:3.1.4-SNAPSHOT
347 8) Deploy the new snapshot as a placeholder for the next release. It
348 will go to the snapshot repository of course:
362 the version from 3.1.3-SNAPSHOT to 3.1.3.
365 release-3.1.3 directory and change the version from 3.1.3-SNAPSHOT
367 pom.xml references from 3.1.3-SNAPSHOT to 3.1.3 as we are now
381 [INFO] Parent was org.antlr:antlr-master:3.1.3-SNAPSHOT,
384 [INFO] Parent was org.antlr:antlr-master:3.1.3-SNAPSHOT,
387 [INFO] Parent was org.antlr:antlr-master:3.1.3-SNAPSHOT,
434 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx target/antlr-master-3.1.4-SNAPSHOT-completejar.jar