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 might be to create a task that filters the source
tree in place as a separate gradle step. If the sources are updated in
place, a cleanup mechanism will be needed to restore the working copy to
its unmodified state between builds. Internally we use the Team City
swabra plugin to accomplish that goal.
David
On 4/11/2023 11:29 AM, Volker Lamp wrote:
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 5.7.0 migration tool
would be useful for Tapestry users to migrate their own code.
I'm not a Gradle expert, but willing to give it a shot. Will let you know if I
come up with anything useful. Will also let you know if I get stuck so the wise
guys can hopefully help me out :)
[1]
https://blogs.eclipse.org/post/mike-milinkovich/jakarta-ee-9-delivers-big-bang
Volker
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
