Open mysticfall opened 11 years ago
Unfortunately, it seems source level compatibility 1.7 also mandates binary compatibility of 1.7 which is not acceptable for our runtime requirements. So, we should defer this issue indefinately until most of the potential users upgrade to Java 7.
Does binary compatibility means that it will be required to run pivot4j on jvm7 if you change source code level to 1.7? Is this the only hurdle?
@kiteRk Yes, you're right. It's basically a marketing decision, namely that if we should force our users to use Java 7+ or not.
I deferred resolving this issue because I thought we better not hinder potential users from trying out our project, as not very few people are stuck with the older JVM for various reasons(i.e. corporate policy).
I'm not sure, but I think by the time we're hitting 1.0, most of the users would be on Java 7+ so we might revisit this issue then.
To leverage the new syntactic improvements (i.e. try-with statement), we need to change source code compatibility to Java 1.7.