Re: [OT] Jakarta package change

2019-05-08 Thread Rémy Maucherat
On Wed, May 8, 2019 at 6:22 PM Christopher Schultz < ch...@christopherschultz.net> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Mark, > > On 5/7/19 06:31, Mark Thomas wrote: > > Rather than announcing a solution, how about we announce that we > > will continue to support the java

Re: [OT] Jakarta package change

2019-05-08 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 5/7/19 06:31, Mark Thomas wrote: > Rather than announcing a solution, how about we announce that we > will continue to support the javax.* APIS (Servlet 4.0, JSP 2.3, EL > 3.0, WebSocket 1.1 and JASPIC 1.1) until at least 31 Dec 2030*. > No

Re: Jakarta package change

2019-05-07 Thread Mark Struberg
Yes, the first step is just trying out what we could have missed. And of course this would be tc-10. The first quick and dirty hack is alive: https://github.com/struberg/tomcat/tree/jakarta You first need to compile the geronimo-jakarta specs locally from https://svn.apache.org/repos/asf/geronim

Re: Jakarta package change

2019-05-07 Thread Rémy Maucherat
On Tue, May 7, 2019 at 7:33 PM Mark Struberg wrote: > Hi folks! > > Yes, I'm right now playing with it. > For a little more background and overview I've written up a blog post: > > https://struberg.wordpress.com/2019/05/06/the-way-forward-for-jakartaee-packages/ > > I've also already started to m

Re: Jakarta package change

2019-05-07 Thread Romain Manni-Bucau
I agree with the 2030 statement but it also means not replacing javax by jakarta is saner because it avoids to duplicate and make ambiguous the API and also reduce maintenance cost. It also keeps tomcat embedded working - classloader hacks or javaagent can be tricky to keep performing well with rec

Re: Jakarta package change

2019-05-07 Thread Mark Struberg
Hi folks! Yes, I'm right now playing with it. For a little more background and overview I've written up a blog post: https://struberg.wordpress.com/2019/05/06/the-way-forward-for-jakartaee-packages/ I've also already started to migrate a few spec packages. The current work in progress is availabl

Re: Jakarta package change

2019-05-07 Thread Rémy Maucherat
On Tue, May 7, 2019 at 12:31 PM Mark Thomas wrote: > On 07/05/2019 08:05, Rémy Maucherat wrote: > > Hi, > > > > Background information: > > https://eclipse-foundation.blog/2019/05/03/jakarta-ee-java-trademarks/ > > > > So this is obviously a large breaking change. While there are plenty of > > op

Re: Jakarta package change

2019-05-07 Thread Rémy Maucherat
On Tue, May 7, 2019 at 10:31 AM Emmanuel Bourg wrote: > Le 07/05/2019 à 09:05, Rémy Maucherat a écrit : > > > - Maintain a Tomcat 9.x "forever" with Servlet 4.0. As a result, all the > > APIs in Tomcat 9 can remain javax.* and users with "old" applications > will > > still have an up to date full

Re: Jakarta package change

2019-05-07 Thread Mark Thomas
On 07/05/2019 08:05, Rémy Maucherat wrote: > Hi, > > Background information: > https://eclipse-foundation.blog/2019/05/03/jakarta-ee-java-trademarks/ > > So this is obviously a large breaking change. While there are plenty of > options, there is a simple one too: > - Maintain a Tomcat 9.x "foreve

Re: Jakarta package change

2019-05-07 Thread Emmanuel Bourg
Le 07/05/2019 à 09:05, Rémy Maucherat a écrit : > - Maintain a Tomcat 9.x "forever" with Servlet 4.0. As a result, all the > APIs in Tomcat 9 can remain javax.* and users with "old" applications will > still have an up to date fully compatible container for them. +1 > - Have a Tomcat 10 with all

Jakarta package change

2019-05-07 Thread Rémy Maucherat
Hi, Background information: https://eclipse-foundation.blog/2019/05/03/jakarta-ee-java-trademarks/ So this is obviously a large breaking change. While there are plenty of options, there is a simple one too: - Maintain a Tomcat 9.x "forever" with Servlet 4.0. As a result, all the APIs in Tomcat 9