Skip to content
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

Closed
4 tasks done
kazuki43zoo opened this issue Mar 16, 2018 · 6 comments · Fixed by #1209
Closed
4 tasks done

Drop support for JDK 1.6 and 1.7 at build definitions #1207

kazuki43zoo opened this issue Mar 16, 2018 · 6 comments · Fixed by #1209
Assignees
Labels
enhancement Improve a feature or add a new feature no backward compatibility Includes change no backward compatibility for previous version
Milestone

Comments

@kazuki43zoo
Copy link
Member

kazuki43zoo commented Mar 16, 2018

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.

@kazuki43zoo kazuki43zoo added this to the 3.5.0 milestone Mar 16, 2018
@jeffgbutler
Copy link
Member

Does JDK 7 actually benefit anyone? Maybe we should jump to 8.

@kazuki43zoo
Copy link
Member Author

Can jump to JDK 8 as support policy of MyBatis core? If it is OK, I agree with @jeffgbutler 's opinion.

@harawata
Copy link
Member

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.
Or, maybe the world has become a better place and everybody is using Java 8+?

kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 16, 2018
@kazuki43zoo kazuki43zoo added the no backward compatibility Includes change no backward compatibility for previous version label Mar 16, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 16, 2018
@jeffgbutler
Copy link
Member

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.

@harawata
Copy link
Member

Good point. +1 to requiring Java 8 then.
We can release 3.4.7 for Java 6, 7 users if it's really necessary.

@kazuki43zoo kazuki43zoo changed the title Drop support for JDK 1.6 Drop support for JDK 1.6 and 1.7 Mar 16, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 16, 2018
@h3adache
Copy link
Member

We had this discussion on the dev list I believe.
I'm would definitely support @jeffgbutler's idea though. The sooner we move to JDK 8 the better

kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 16, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 16, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 16, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 16, 2018
* 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
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 16, 2018
* 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
@kazuki43zoo kazuki43zoo changed the title Drop support for JDK 1.6 and 1.7 Drop support for JDK 1.6 and 1.7 at build definitions Mar 17, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 17, 2018
@kazuki43zoo kazuki43zoo added the enhancement Improve a feature or add a new feature label Mar 18, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 19, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 19, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 19, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 19, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 19, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 19, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 19, 2018
* 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
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 19, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 19, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Mar 19, 2018
@kazuki43zoo kazuki43zoo self-assigned this Mar 19, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Jun 23, 2018
kazuki43zoo added a commit to kazuki43zoo/mybatis-3 that referenced this issue Jun 23, 2018
pulllock pushed a commit to pulllock/mybatis-3 that referenced this issue Oct 19, 2023
pulllock pushed a commit to pulllock/mybatis-3 that referenced this issue Oct 19, 2023
pulllock pushed a commit to pulllock/mybatis-3 that referenced this issue Oct 19, 2023
pulllock pushed a commit to pulllock/mybatis-3 that referenced this issue Oct 19, 2023
pulllock pushed a commit to pulllock/mybatis-3 that referenced this issue Oct 19, 2023
pulllock pushed a commit to pulllock/mybatis-3 that referenced this issue Oct 19, 2023
pulllock pushed a commit to pulllock/mybatis-3 that referenced this issue Oct 19, 2023
* 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
pulllock pushed a commit to pulllock/mybatis-3 that referenced this issue Oct 19, 2023
pulllock pushed a commit to pulllock/mybatis-3 that referenced this issue Oct 19, 2023
pulllock pushed a commit to pulllock/mybatis-3 that referenced this issue Oct 19, 2023
pulllock pushed a commit to pulllock/mybatis-3 that referenced this issue Oct 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improve a feature or add a new feature no backward compatibility Includes change no backward compatibility for previous version
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants