[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-community] JCP or not (fork of Re: On Naming)
|
I don't think backward compatibility has stopped to be a concern for people. At least for me, BC is one of the key strengths of Java EE.
I've recently had to migrate some Java EE 5 applications from GlassFish 2 to WildFly 10 with no susprises and minimal changes (basically propietary deployment descriptors). Java EE image would be seriously damaged if sd break this promise.
Yet I agree we should experiment more and move faster, but there Microprofile comes to play, and even Java 9 incubator modules.
Wether we use the JCP or not, the same rules should be maintained IMO.
Regards,
Guillermo González de Agüero
I think we could actually break backwards compatibility moving forward. I don't say that lightly, as in "just burn it all to the ground", it's just there are different concerns for the community now then there were 5 years ago, let alone 10 years.
One thing I would love to see now is more of a focus on lighterweight and composability - to make the server smaller (disk and memory) as well as Maven dependencies smaller. There is a good chunk of the the full spec that most developers don't need or care about.
_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community