Lack of language level restrictions in the pom

Question

Lack of language level restrictions in the pom

westonal opened this issue 8 years ago · comments

Problem: Build servers build against Java 1.7
Lack of language restriction in POM means that locally Java 1.8 is acceptable and it is not apparent until we start PR that we have used some Java 8 method/class.

The ide and local build should restrict language use, the simplest way would be to include this in the POM.

Dan Markov · Answer 1 · Mon May 23 2016 17:46:45 GMT+0800 (China Standard Time)

@yegor256 dispatch this issue please, see par.21

Alan Evans · Answer 2 · Sat Jun 18 2016 17:29:25 GMT+0800 (China Standard Time)

@dmarkov what's happening with this task?

Yegor Bugayenko · Answer 3 · Thu Jun 23 2016 06:59:22 GMT+0800 (China Standard Time)

@westonized our JDK version is 1.6 and inherit that from jcabi-parent POM. I don't think we should duplicate that information in our own POM. or I didn't understand the question?

Alan Evans · Answer 4 · Thu Jun 23 2016 07:30:38 GMT+0800 (China Standard Time)

@yegor256 If it is inherited, how come I have no issues building against java 1.8 features and methods locally. And I only discover it's a problem when I start a pull request.

That is I can locally build this project with mvn clean install -Pqulice referencing Java 8 methods and classes.

Alan Evans · Answer 5 · Fri Jun 24 2016 03:21:38 GMT+0800 (China Standard Time)

@yegor256 It looks like you have done what this task is suggesting anyway in the pom here: bc4391c

Yegor Bugayenko · Answer 6 · Tue Jun 28 2016 03:03:59 GMT+0800 (China Standard Time)

@westonized OK, I'm closing. thanks.