Re: javax.servlet -> jakarta.servlet

2023-04-11 Thread Volker Lamp
Hi David > A gradle plugin is not a bad idea and would be relatively > straightforward to implement. We have developed many gradle plugins over > the years and are open to contributing to that effort. Excellent. Help is always welcome. > The simplest approach might be to create a task that

Re: javax.servlet -> jakarta.servlet

2023-04-11 Thread David Taylor
Hello all, I am glad to hear there is interest in moving forward on the migration. A gradle plugin is not a bad idea and would be relatively straightforward to implement. We have developed many gradle plugins over the years and are open to contributing to that effort. The simplest approach

Re: javax.servlet -> jakarta.servlet

2023-04-11 Thread Volker Lamp
Hello all, As time progresses it becomes more urgent we tackle this. As I understand the Big Bang [1], it's actually just updating the package names indeed. In my opinion, doing it all in Gradle would be the way to go for the Tapestry code base. Probably writing a Gradle plugin. The Tapestry