Chris, and the rest of the TC team
cs> Note that Java 10 will auto-migrate older applications for you
cs> without modification. It's kind of a friendly bootstrapping feature
cs> to help developers make the transition to pre-Jakarta-EE to
cs> port-Jakarta-EE.
Thaaanks! :-)
cs> the transition
Thank you very much, for your response and time...
With time, I will see as normal the new versions
-jose
On Mon, Mar 14, 2022 at 5:36 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> Jose,
>
> On 3/14/22 10:55, Jose Illescas wrote:
> > Thank You for your response and link...
> Christopher Schultz wrote:
> So we're sorry if our decisions about the version numbering scheme are
> disturbing you.
Just to add another data point:
I don’t care about the numbering scheme as long as the code does what
I need it to do. Tomcat works for me and does it very well.
I have to
Jose,
On 3/14/22 10:55, Jose Illescas wrote:
Thank You for your response and link...
But I disagree with their opinion, because the "jakartization" of packages
it is a very rupturist change:
All libraries, frameworks and applications that run over a j2ee container
(tomcat, jetty, jboss...)
Thank You for your response and link...
But I disagree with their opinion, because the "jakartization" of packages
it is a very rupturist change:
All libraries, frameworks and applications that run over a j2ee container
(tomcat, jetty, jboss...) must be changed or adapted. For me, this is
enough
On 13/03/2022 13:29, Jose Illescas wrote:
I think that Tomcat mayor version must be change when updateing some of
their specs (servlet/jsp7/websockets/...)
This strategy allow us to refer to tomcat with: Tomcat-9 or Tomcat-10
avoiding annoying names as tomcat-10.0.X or tomcat-10.1.X
IMHO
