Make sure that the code is compatible with JDK 1.6 #1169

Closed
timowest opened this Issue Feb 7, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@timowest
Member

timowest commented Feb 7, 2015

Travis builds with different JDK versions doesn't cover this requirement, since Querydsl can't be built anymore with JDK 1.6. Still the result should be compatible with JDK 1.6.

This looks like a promising solution http://eclipsesource.com/blogs/2014/05/09/ensure-class-library-compatibility-in-a-maven-build/

@timowest timowest added this to the 4.0.0 milestone Feb 7, 2015

@Shredder121

This comment has been minimized.

Show comment
Hide comment
@Shredder121

Shredder121 Feb 7, 2015

Member

What I do when I want to try JDK6 is build it using JDK7, then switch JDK's and only run the tests.

Isn't that possible using Travis?

  • jdk_switch jdk7
  • build
  • jdk_switch jdk6
  • test

For reference: Switching JDKs Within One Job

Member

Shredder121 commented Feb 7, 2015

What I do when I want to try JDK6 is build it using JDK7, then switch JDK's and only run the tests.

Isn't that possible using Travis?

  • jdk_switch jdk7
  • build
  • jdk_switch jdk6
  • test

For reference: Switching JDKs Within One Job

@timowest

This comment has been minimized.

Show comment
Hide comment
@timowest

timowest Feb 7, 2015

Member

You are right. I wasn't aware of this option. I will try the travis config customization then.

Member

timowest commented Feb 7, 2015

You are right. I wasn't aware of this option. I will try the travis config customization then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment