Re: [ee4j-community] JCP or not (fork of Re: On Naming)

[Michael Nascimento <misterm@xxxxxxxxx>]

On Mon, Oct 9, 2017 at 12:28 PM, Josh Juneau <juneau001@xxxxxxxxx> wrote:

Just a quick note to mention that we are always moving forward, and sometimes backward compatibility has to break to bring in new features.  For instance, JSF 2.3 requires the use of Java 8, which is basically breaking backward compatibility for that framework.  

This is not breaking backward compatibility, in the same way that to use the Java SE 8 features you have to upgrade to Java SE.

 

I don't necessarily think that we need to apply the concept of backward compatibility at the EE4J level,

That's how it has been and it's, for bad or for worse, one crucial reason most enterprises trust it. It's the main selling point for Java SE as well.

Regards,

Michael