[
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?
|
Deprecation as defined by the Java EE spec is basically a formal process of warning users that no progress/new features can be expected. It doesn't necessarily mean classes and packages are annotated @Deprecated so end users shouldn't see any difference.
I would tend to agree with Adam but would need to really understand the real world technical implication of making SOAP deprecated
for a proposed period of 10 years or even removing it completely for that matter. Does this mean that code which uses these libraries
will see deprecation warnings for 10 years when they go to do a simple compile? If so, 10 years seems like a long time to spit out warnings.
Is there already a precedence for deprecation which java developers will already expect to be maintained moving forward?
I know some people and even tools that take such warnings very serious when they consider technical debt and long term road mapping
so this is certainly worth resolving in the near term.
Regards,
_______________________________________________
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