-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Bump Java version to 1.8 #28
Conversation
Signed-off-by: Markus KARG <markus@headcrashing.eu>
I wonder whether we could switch to integer versions of this POM w/ minor releases which do not really make sense with parents. I'd happy if we could move to Parent version 7. |
Just to understand you correctly: You want to replace "1.7" by "7", but not by "8"? |
No, no. I was completely referring to Line 25 in 0b9b7ac
|
Understood, but what is the process to do that? Can we simply do that in this PR (in the sense of "we need to step up because of Java 8"), or shouldn't we open another PR first just for that (in the sense of "it is time to step up now anyways, so in turn we could then do Java 8")? See, these are different discussions... |
I would prefer to have a new version of the parent POM with a separate PR and then this one. |
I'd also release of currently open components a last Java 7 version before moving to the new parent POM version. |
Understood. So here we go: #29 :-) |
Ok, need to let you do that -- I cannot perform releases AFAIK (or have not found out how to). |
Java SE 8 is supported since 2014, and should be available on most platforms meanwhile. It provides new APIs which are benficial to Plexus, e. g. improved IO handling, etc. I'd like to start a discussion, when to align Plexus with Maven and make Java 8 the minimum supported version.