Re: [DISCUSS] Java 8, breaking API changes, MetaModel 5.0?

The maybe we should even hold back METAMODEL-6 to avoid breaking the method linking/signature of executeUpdate(...) too early. It also always helps with a few big functional improvements in a major release like a 5.0 :-) I will start making a 'version' in JIRA for 5.0 and assign a few stories (men

Re: [DISCUSS] Java 8, breaking API changes, MetaModel 5.0?

This is a great idea, I was about to suggest the creation of a wish-list of changes that could be implemented using Java 8. Alberto Rodriguez Vía de las dos Castillas, 33, Ática 4, 3ª Planta 28224 Pozuelo de Alarcón, Madrid Tel: +34 91 828 6473 // www.stratio.com // *@stratiobd

[DISCUSS] Java 8, breaking API changes, MetaModel 5.0?

Hi all, Maybe some of you have noticed the discussions going on regarding the PR for METAMODEL-8 [1] in which the use of Java 8's Optional class turned into a hot topic. Currently we still support Java 7 and I think it's sane to keep supporting it for a while. But on the other hand there are featu