I think Java 8 can have good impact on libraries too. For example it will greatly help to remove dependency of commons-collections, this alone is a great benefit. Plus we'll get opportunity to use standard functional interfaces in API (we are using custom defined for that), include java8 lib into the core and I suppose there are other areas where Java 8 can help.
On Thu, Jul 27, 2017 at 2:40 PM, Aristedes Maniatis <[email protected]> wrote: > On 26/7/17 7:52PM, Nikita Timofeev wrote: >> Java 7 has reached EOL couple years ago and Java 9 will be there in >> this September, so I think support for new Java version is more >> important, and that is not fully possible without dropping Java 7 (at >> least it's impossible to have compatibility with 7,8 and 9 for MacOS >> version of the Modeler). > > It possible to update the version of Java just for the modeler. That way we > can keep the older version for the libraries (until we really want to use new > features of Java) and upgrade the modeler much more quickly. > > For example, I'd be in favour of moving 4.1 Modeler directly to Java 9. Yes, > that sounds slightly mad, but Swing/FX continues to improve and Java 9 > introduces better font handing and high resolution Windows displays. > Developers should have little trouble running a really recent version of Java > for the modeler even when servers are still several major releases behind. > > For us, we have trouble moving to Java 8 since we are stuck on a slightly old > version of Apache Tapestry. > > > Are there Java 8 features we want to use in the Cayenne libraries? > > Ari > > > -- > --------------------------> > Aristedes Maniatis > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A -- Best regards, Nikita Timofeev
