Github user kaspersorensen commented on the pull request:
https://github.com/apache/metamodel/pull/77#issuecomment-164198957
I don't like the idea of suddenly changing our requirement from Java 7 to
Java 8, just because a new feature could benefit from it. I know I'm being a
party-pooper, but I think that kind of stuff needs to be planned and handled in
a way where we give people more choice about when they take the step to Java 8.
If nothing else, the application I (we ;-)) work on most has roughly 40% users
that still are on Java 7, so we wanted to not retire it just yet... But soon
for sure. But other companies are surely more conservative and will wait
longer. My final word on Java 8 would be: Probably there are _many_ more API
improvements we could make if we decide to go with Java 8. I would suggest we
start a separate topic about that and consider that a part of a future
MetaModel 5.0 with renewed API in many places.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
