Add support for Travis CI (http://travis-ci.org).

[stefanbirkner]

I like the Travis CI because it automatically runs ant test for each of my branches. Every developer can create a Travis account and enable this feature for its fork.

One nice feature is its support for Github's Commit Status API. Github's web interface shows us the CI result for each pull request.

Would be nice if we add support for Travis CI. It does not have to replace Cloudbee's Jenkins.

Any thoughts?

[kcooney]

I thought we were migrating to maven (away from ant) for builds

[stefanbirkner]

Do you know the current status of the Maven migration? I still use Ant for building JUnit.

[kcooney]

Not sure

@dsaff Do we plan to continue to support both Ant and Maven for building JUnit?

[dsaff]

I think that the plan is that maven becomes the build of record, with ant there for legacy. We should probably make a comment in the ant file to that effect.

[stefanbirkner]

How about removing ant completely? No build.xml - no misunderstanding. And only one file to be maintained.

[askoog]

+1 for only having one build system.

Currently, the https://github.com/junit-team/junit/blob/master/CONTRIBUTING.md file specifies that you should use ant to build, but the https://github.com/junit-team/junit/blob/master/BUILDING file says the project is built with maven...

[dsaff]

I'm OK with deprecating ant.

Stefan, can you do the legwork of contacting the mailing list and finding out if anyone's still depending on the ant build?

[Tibor17]

+1 to maintain Maven build system only

[dsaff]

Keeping separate issues separate, can we use Travis CI with maven?

[stefanbirkner]

Yes, it is the default. Should I squash the two commits?

[ansell]

Travis CI works well with Maven. It also supports a recent build of oracle-jdk-8 (b117 I think), so you can test against that without installing it locally.

[ansell]

Could also add oraclejdk8 here

[stefanbirkner]

Sorry, I can't by now because of issue #749.

[ansell]

Reference documentation for Java builds on Travis CI is at:

http://about.travis-ci.org/docs/user/languages/java/

That specifies that Maven will be chosen (in automatic mode) over Ant if both are pom.xml and build.xml are found. If you did want to build with ant you would need to specify it in the .travis.yml file.

[dsaff]

Stefan,

Sure, squash away! Thanks.

[stefanbirkner]

Squashed.

[dsaff]

Many thanks! Can you add to the release notes?

[stefanbirkner]

Done.

[jvz]

Random note to add about the Maven-only build: you can use Maven to generate an Ant build anyways. There's no point in supporting Ant after you migrate to Maven.