|Re: [ee4j-community] Some guidelines for Maintenance Releases (MRs) of Java EE 8 Specifications|
This needs to be formalized, but as an example of an extension of
the existing javax namespace, there is an existing
javax.servlet.http package. Let's say an http3 standard came
out, and EE4J wanted a new version of the Servlet spec to support
it, then that's something that might be considered an extension
for which a new javax.servlet.http3 package might be created for.
However if someone wanted to create a net new specification in a
new functional area for which there is currently no specification
or JSR we would expect that a net new package using a new
namespace (other than javax.*) to be used.
The examples above are intended for when EE4J is in steady state
operation. JSR 382 was introduced during the transition period.
I assume we will work something out for it which makes sense for
the EE4J community.
On 1/8/18 7:10 PM, Werner Keil wrote: