-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drop support for JDK 1.6 and 1.7 at build definitions #1207
Comments
Does JDK 7 actually benefit anyone? Maybe we should jump to 8. |
Can jump to JDK 8 as support policy of MyBatis core? If it is OK, I agree with @jeffgbutler 's opinion. |
It's more like to support users who are using (or want to use) MyBatis in Java 7 projects that are not easily upgraded to newer versions for various reasons. |
I am trapped in the JDK7 world too, unfortunately. My point is that I don't think there is enough difference between JDK6 and JDK7 to make it worth it. What would we actually change in the code for JDK7? Switch to diamond syntax? Yawn. I freely admit that I may be missing something cool we could do in JDK7 - so please let me know if there is something like that. For my commercial projects, version 3.4.6 has everything I need and more. I would support version 3.5.0 going to JDK8 and stating clearly that 3.4.6 is the version we support on JDK6 and JDK7. |
Good point. +1 to requiring Java 8 then. |
We had this discussion on the dev list I believe. |
* log4j-core 2.3 -> 2.5 * cglib 3.2.5 -> 3.2.6 * junit-vintage-engine 4.12.2 -> 5.1.0 * hsqldb 2.3.5 -> 2.4.0 * derby 10.12.1.1 -> 10.14.1.0 * mockito-core 2.12.0 -> 2.16.0 * commons-dbcp 1.x -> commons-dbcp2 2.2.0 * jboss-transaction-api_1.2_spec 1.0.1 -> 1.1.1 * postgresql 42.1.4.jre6 -> 42.2.1 * assertj-core 1.7.1 -> 3.9.1 * catch-exception 1.4.4 -> 1.4.6 * postgresql-embedded 2.5 -> 2.8
* log4j-core 2.3 -> 2.5 * cglib 3.2.5 -> 3.2.6 * junit-vintage-engine 4.12.2 -> 5.1.0 * hsqldb 2.3.5 -> 2.4.0 * derby 10.12.1.1 -> 10.14.1.0 * mockito-core 2.12.0 -> 2.16.0 * commons-dbcp 1.x -> commons-dbcp2 2.2.0 * jboss-transaction-api_1.2_spec 1.0.1 -> 1.1.1 * postgresql 42.1.4.jre6 -> 42.2.1 * assertj-core 1.7.1 -> 3.9.1 * catch-exception 1.4.4 -> 1.4.6 * postgresql-embedded 2.5 -> 2.8
* log4j-core 2.3 -> 2.5 * cglib 3.2.5 -> 3.2.6 * junit-vintage-engine 4.12.2 -> 5.1.0 * hsqldb 2.3.5 -> 2.4.0 * derby 10.12.1.1 -> 10.14.1.0 * mockito-core 2.12.0 -> 2.16.0 * commons-dbcp 1.x -> commons-dbcp2 2.2.0 * jboss-transaction-api_1.2_spec 1.0.1 -> 1.1.1 * postgresql 42.1.4.jre6 -> 42.2.1 * assertj-core 1.7.1 -> 3.9.1 * catch-exception 1.4.4 -> 1.4.6 * postgresql-embedded 2.5 -> 2.8
* log4j-core 2.3 -> 2.5 * cglib 3.2.5 -> 3.2.6 * junit-vintage-engine 4.12.2 -> 5.1.0 * hsqldb 2.3.5 -> 2.4.0 * derby 10.12.1.1 -> 10.14.1.0 * mockito-core 2.12.0 -> 2.16.0 * commons-dbcp 1.x -> commons-dbcp2 2.2.0 * jboss-transaction-api_1.2_spec 1.0.1 -> 1.1.1 * postgresql 42.1.4.jre6 -> 42.2.1 * assertj-core 1.7.1 -> 3.9.1 * catch-exception 1.4.4 -> 1.4.6 * postgresql-embedded 2.5 -> 2.8
The MyBatis 3.5.0 will support JDK 8+.
Tasks
Notes
This issue will fix only build definition. I will propose that source code polishing performs using other issues.
The text was updated successfully, but these errors were encountered: