Hi Guilio, the whole javax/jakarta forced migration was a mess for many open-source projects, especially when they wanted to support both variants.
You updated a project with a 17-year-old Tapestry version using another repository that’s almost 10 years without any updates? Even moving only the version from javax to Jakarta can be quite a lot of work… We actually discussed how to improve working with third-party projects, but “taking charge” and including them directly into the Tapestry project is almost never a viable option. We have quite limited resources, and every new module/project we add to the main project creates a long-term commitment to keep it up-to-date, react to any upstream issues, and make sure dependencies don’t clash, etc. Furthermore, a project might not even have a compatible license to begin with. tapestry-boot, for example, lacks one completely, making it impossible to use that code in any way. >From the GitHub docs: “However, without a license, the default copyright laws apply, meaning that you retain all rights to your source code and no one may reproduce, distribute, or create derivative works from your work.” https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository#choosing-the-right-license The tapestry-eclipse plugin is a different beast. My colleagues and I use it every day, and I thought about forking it in the past. But Dmitry keeps it running, there’s a software update-site, and it works for the parts we use it for. Let’s say we’d fork it into Tapestry project. I’ve never worked on an Eclipse plugin before, and as far as I know, none of the other active devs have, too. So we’d need to support a project that no one knows how to actually do. If a new Eclipse version is released and breaks it, the community now expects us to fix it, draining resources we could use for other things. And what about IntelliJ? Why is there only an “official” Eclipse plugin? There are so many cool things out there that would be nice to be included directly in Tapestry. But if we start including them, there’s no end to the work and additional technical debt it would create… But there’s still something we want to do, as there are a lot of awesome third-party projects out there that many people have never heard about, us included! We’d like to make them more visible and support them to be more up-to-date. We’re thinking about creating a “community umbrella” for third-party projects. One thing would be “awesome” list for what’s out there, like https://github.com/akullpp/awesome-java The other thing would be allowing people to bring their project under the umbrella, so they are discoverable at one place and are closer to the primary project. Being its own thing, the umbrella would not same commitment/expectations as the primary project does. The community projects might not get updated as soon as a new Tapestry version is released. But having them under one roof makes problems more visible, and anyone can provide a PR to update, and they can have maintainers outside of Apache committers. Of course, there are still a lot of question marks to such an idea… like how to keep it separated from Apache Tapestry, to not bring in trademark/license issues. What format should the umbrella have? GitHub organisation? What projects should be eligible? Who decides? ... Our current focus as a project is on strengthening the foundation. The next release, 5.10, will have a totally revamped build/Gradle setup that hopefully will serve us well for a few years. A new website is almost done, with versioned documentation and an easier way to participate. There are a lot of things in the works currently, but also even more things that need to be done in the future. You have to remember that we are all volunteers and our resources are limited. We try our best to move the project forward. But that also means that some things will take longer than others, or never get done at all. And it might not be easily clear why something was prioritized, or not. But as this is open-source, anyone is invited to join and contribute ;-) Cheers Ben On Sat, May 9, 2026 at 5:32 AM Giulio Micali <[email protected]> wrote: > Switched to it 2 weeks ago from an old 5.1 personal project but: > - i spent 1 week to upgrade tapestry-boot with the *-jakarta libraries, and > honestly i made a mess with the filter, not knowing what i was doing. > - There were "javax.servlet" Exceptions everywhere, I found the jakarta > maven deps just by accident...ecc... > A waste of time. > > Isn't it time to take charge of that project ad include it in your packages > ? and the same for the Eclipse plugin. > They are not mantained by almost 10 years. > > Just my 2 cents, > > Cheers, > Giulio > > Il giorno mer 29 apr 2026 alle ore 14:47 Thiago H. de Paula Figueiredo < > [email protected]> ha scritto: > > > Hello! > > > > Tapestry 5.9.1 has been released and it's a recommended upgrade for > > projects using Tapestry 5.7.0+. > > > > Highlights: > > > > TAP5-2814 Upgrade ASM to 9.9 > > TAP5-2758 Constructor/Builder injection should support @Symbol for > > List/Collection/Map even without @Inject > > TAP5-2813 NPE when @Cached applied to method returning a generic type > > in multiple classloader mode > > > > Happy coding! > > > > -- > > Thiago H. de Paula Figueiredo > > Software developer/engineer > > Apache Tapestry consultant, committer and project management committee > > member > > You can sponsor my work on Tapestry at > > https://github.com/sponsors/machina-br > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > -- > Giulio Micali >
