Skip to content

Upgrade to Java7 #57

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

Closed
rfscholte opened this issue Jul 18, 2016 · 3 comments
Closed

Upgrade to Java7 #57

rfscholte opened this issue Jul 18, 2016 · 3 comments
Milestone

Comments

@rfscholte
Copy link
Member

No description provided.

rfscholte added a commit that referenced this issue Jul 18, 2016
@TobiX
Copy link
Contributor

TobiX commented Jul 29, 2016

Was that necessary? I have some legacy projects which still require Java 6 to build... This means I would need to continue using my own fork instead of the stock exec-maven-plugin - Can we at least keep Java 6 compatibility for the next release?

@rfscholte
Copy link
Member Author

Java7 is the current default for all mojohaus plugins. And we're talking about the runtime, which can be a different version that the JDK you use to build your project. Have a look at https://maven.apache.org/guides/mini/guide-using-toolchains.html to see how you can use different versions for the Maven runtime and the JDK build time.

@TobiX
Copy link
Contributor

TobiX commented Aug 22, 2016

Ah, sorry. We're already using toolchains. I was under the impression that M2E used the project Java version to call Maven with, but it uses the workspace JDK. Which just means I have to roll out a new Eclipse workspace for my team ;) - Disregard my comment.

@rfscholte rfscholte added this to the 1.6.0 milestone Mar 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants