a441b297af
fix javadoc arg in pom, update javadoc instructions
2015-10-31 16:40:42 -07:00
c07aa4ede1
[maven-release-plugin] prepare for next development iteration
2015-08-20 12:11:58 -07:00
3611fde621
[maven-release-plugin] prepare release 4.5.1-1
2015-08-20 12:11:55 -07:00
3d181af904
[maven-release-plugin] prepare for next development iteration
2015-07-15 14:45:48 -07:00
79dae1e6f6
[maven-release-plugin] prepare release 4.5.1
2015-07-15 14:45:45 -07:00
398f7fcf53
Run all Java target tests by default
...
And we will use the "tests" profile to initiate the tests for the rest of the targets.
2015-06-29 22:03:16 -04:00
c129166e69
we are calling the test generator directly because Jason said that was much easier than a plug-in that used during the build itself; simplifying to remove that plug-in.
2015-06-29 18:32:51 -07:00
661a565448
rename rts to tests to make it more understandable
2015-06-29 18:26:44 -07:00
9de674a6fd
Correct name of runtime suite directory
2015-06-29 21:23:55 -04:00
5d45e15601
Place the runtime and tool test suites in a separate profile
2015-06-29 21:22:14 -04:00
fd13f137f2
All projects are now building and tests passing from Maven
2015-06-29 18:09:39 -07:00
8c255b9a12
trying to get tests to run
2015-06-29 18:09:38 -07:00
f5b48efd46
manual cherrypick of Sam's d74781d2fe
2015-06-29 18:09:38 -07:00
dec5d26a3d
tweak pom so it compiles in `compile` phase and `install` phase but doesn't run tests correctly.
2015-06-29 18:09:37 -07:00
46202d98a2
Integrating tests for all supported targets
...
- A profile "rts" has been created which runs the integration tests. By default the the project containing the runtimes tests will not run so that users casually checking out and building the project do not have to install the tools required to test all the supported Antlr targets.
- The base test classes that are required for running the integration tests are downloaded from the other Antlr repos, dynamically added to the compile classpath and used by the currently checked in integration tests
To run the the full build with all the integration tests use the following:
mvn clean install -Prts
2015-06-24 13:45:40 -04:00
8beec18283
Add Maven build
...
Account for the following:
- deploying snapshots to OSSRH
- releasing to Maven Central
- Shaded JAR including the treelayout dependency
- OSGi manifest
- remove Eclipse IDE metadata for clean import
- remove IDEA IDE metadata for clean import
2015-06-19 11:13:24 -07:00
6d9d60ccda
Copy stuff from the root pom to the individual poms and remove the root. Remove dependency on the annotations artifact which no longer exists. hardcode the version number everywhere to make sure I don't use a variable that doesn't exist. update bild so that it uses a new maven_deploy() function I put into bilder.py
2015-01-13 17:29:38 -08:00
6298e990fc
add snapshot repository xml filth inside pom
2015-01-12 21:31:54 -08:00
cf26bc8a33
make it 4.5-SNAPSHOT
2015-01-12 16:56:41 -08:00
8c05364099
set versions to 4.5
2015-01-10 10:12:02 -08:00
91206869c5
Prepare for next development iteration
2014-06-28 22:40:33 -05:00
7d88b0106a
[maven-release-plugin] prepare for next development iteration
2014-06-18 21:25:44 -05:00
201eeb147d
[maven-release-plugin] prepare release 4.3
2014-06-18 21:24:24 -05:00
3378be9c79
Update all version numbers for consistency prior to the 4.3 release
2014-06-18 19:37:29 -05:00
7e2bf4a2d5
[maven-release-plugin] prepare for next development iteration
2014-04-06 21:19:40 -05:00
736a5f5905
[maven-release-plugin] prepare release 4.2.2
2014-04-06 21:18:12 -05:00
5be18445cd
[maven-release-plugin] prepare for next development iteration
2014-03-25 10:57:46 -05:00
943aaa5d24
[maven-release-plugin] prepare release 4.2.1
2014-03-25 10:57:44 -05:00
06ab99d16d
[maven-release-plugin] prepare for next development iteration
2014-02-04 17:19:12 -06:00
5e05b71e8b
[maven-release-plugin] prepare release 4.2
2014-02-04 17:19:11 -06:00
3d462f29b5
Updated maven release configuration
2014-02-03 22:18:56 -06:00
937c627b16
Move NotNull and Nullable annotations to their own artifact
2014-01-21 14:31:29 -06:00
a55901bc0d
We are working on the 4.2 release
2014-01-19 13:43:57 -06:00
274120c2b6
Now working on release 4.1.1
2013-07-02 19:11:04 -05:00
dbe1390c6f
Update referenced maven plugin version numbers
2013-06-30 12:47:26 -05:00
05f7fc6500
Update development version to 4.1 (from 4.0.1)
2013-06-30 12:46:41 -05:00
ff10afe9e6
Add Jim Idle as a developer to pom.xml
2013-03-27 15:07:09 -05:00
e1cce61400
Development line is now 4.0.1
2013-01-21 19:20:01 -06:00
fc9a0fe96b
Set inceptionYear, organization, and mailingLists; fix scm url
2013-01-21 13:13:08 -06:00
fb865cec3b
Maven builds: if mvn is not run with -Psonatype-oss-release, then 1) javadocs are not generated, 2) source jar is not generated, 3) artifacts are not signed, 4) shaded (complete) jar is not generated. Development cycle install ~4:1 faster, clean+install ~2:1 faster
2013-01-05 05:40:11 -06:00
0ee0de1e06
Maven builds run unit tests in-process by default
2013-01-05 05:40:10 -06:00
4a442562e6
Allow specifying the bootclasspath by the bootclasspath.java5 and bootclasspath.java6 variables
2012-12-07 14:43:13 -06:00
90020850ea
Only show warnings and errors from maven-javadoc-plugin
2012-12-06 13:07:30 -06:00
db32c80265
Fix bootstrap classpath references
2012-12-04 12:58:25 -06:00
b2ab7ab5ac
Rename master artifact to antlr4-master
2012-12-04 12:57:56 -06:00
8a3298e075
Configure the maven-compiler-plugin in the parent POM, including the use of a bootstrap classpath to build a Java 6-compatible jar even when Java 7 is used to build it
2012-11-30 12:28:39 -06:00
af76d3294e
Configure the maven-source-plugin and maven-javadoc-plugin in the parent POM
2012-11-30 12:26:25 -06:00
75a0551308
Update POM to include the Implementation-Title, Implementation-Version, and Implementation-Vendor-Id in the MANIFEST.MF
2012-11-28 22:12:28 -06:00
f264609453
Updated POMs for deploying to sonotype
2012-11-27 23:34:36 -06:00
867a1ec9a8
Specify url in master POM
2012-11-23 13:44:10 -06:00
Terence Parr
parrt
Jason van Zyl
Sam Harwell