Hi Michael > i was wondering, if there is already a plan / timeline to use tapestry > as well with the switch of javax to jakarta. Currently a Huge Migration > from a current environment to new base is blocked due to the dependency > of javax.*. Neccasary dependencies like spring and spring secuirty are > already switched and could be used. > > * Is there already any plan to use the updated part ?
To some extent, yes. The topic was discussed to some extent last summer. See https://lists.apache.org/thread/3r73mjhsvncnywwvqpoho91vp9ldlcv5 for what I understand is the latest state of affairs. Also, a Jira issue (https://issues.apache.org/jira/browse/TAP5-2741) was created to give this a home but no-one has worked on it so far. > Thanks for your support, this would help to clarify internally deadines > and dependencies for an important roadmap. Hopefully this is of some help for your roadmap, even though a timeline would be more useful for you. Volker --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
