[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakarta.ee-community] Why not dropping EARs in Jakarta EE?
|
Btw, my proposal for "stabilized" is not that "the community is not interested on it" but more of a "we don't plan to update it".
In fact I don't like the "Stable" tag as it makes everything else look unstable. I used that term as I was the one used for the other affected Jakarta EE projects to avoid calling them "legacy".
So, just to understand your view, do you think we should get rid of the deprecation process from Java EE?
I don't think it would be a wise idea for a standardizing body to comment/tag on its own specifications based on user opinions or technology direction. IMO, this kind of reflects poorly on its own standardizing processes. It should be left to implementors/vendors on how much value-add they choose to provide on top of these technologies (while supporting others for backward compatibility). Also I think commenting on stability or direction is something that should be left to solution providers or consulting firms. A good example of this might be the ThoughtWorks Technology Radar.
-Mrinal
_______________________________________________
jakarta.ee-community mailing list
jakarta.ee-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jakarta.ee-community
--
Regards,
Guillermo González de Agüero
--
Regards,
Guillermo González de Agüero