search

borisbrodski / Jnario

Executable specifications for Java
jnario.org
3 stars 4 forks source link

Java Version #7

Open ghaith opened 8 years ago

ghaith commented 8 years ago

Should we keep compatibility with older java versions? Currently all manifests have a java 6 dependency. Should we limit the fixes to java 6 compatibility, or would you think it's ok to move to Java 8. The move will also mean a lot of the xtend commited code can be changed to Java 8 as well

Tagging @mrieder if he has input as well

borisbrodski commented 8 years ago

Hello Ghaith,

we will have to move to the Java 8 at some point in the future. Why do you think it's important right now?

When we complete the next release (using Xtext 2.9), Jnario will be able to generate Java 8 code anyway.

Currently IMHO though we should make sure that Jnario survives. Bringing up the next release is essential.

I will add "Migrate to Java 8" to the TODO list here: https://github.com/sebastianbenz/Jnario/issues/160

Cheers, Boris

borisbrodski commented 8 years ago

I think we should stick to the Xtext at this one. When Xtext migrates to Java 8, we can safely do it as well.

ghaith commented 8 years ago

Ok, in that case I'll restrict my environment / current fixes to a Java 6 compliant one. I agree that a move to Java8 might take long, and is probably not necessary for this release. The idea started as we were working on a fix and used a Java 8 class before noticing that we are still using Java 6

riederm commented 7 years ago

I'm close to submitting a branch for xtext.2.11. Xtext2.11 requires java 1.8 so I moved all plugins to java.18

borisbrodski commented 5 years ago

Could you please check, if your commits are present in the current master branch?

I thought, Jnario is still on Java 1.6, since the ASM 5.0.x (required by PegDown) can't handle Java 8 stuff. I replaced PegDown with FlexMark now, so we are free to move forward with the Java versions.