Hello, regarding the recent discussion:
"... And what about IntelliJ?, Why is there only an “official” Eclipse plugin?... " "Official" – Tapestry Plugin for IntelliJ is abandoned and archived as obsolete for some time. As we are still heavily using Tapestry in production, I have tried to modify this plugin all the time to make it still mostly usable with the current IntelliJ IDEA version. As the last IntelliJ version has broken it completely, I have ported the abandoned version: - Convert it to the current IntelliJ plugin architecture (thanks Claude) and ported to Kotlin, - restored original functionality (I didn't know some features ever existed:) ) - Added some little parts our team found useful. So feel free to give them a chance. https://github.com/rar91279/tapestry-plugin I plan to maintain this plugin as long as our production systems are still running Tapestry (this could be a pretty long time :) ). And just my 2 cent to a recent discussion around "new" approaches to web development. Yes, current frameworks like Spring and Quarkus are pretty handy to start and work with. But Tapestry give you full control about how to bootstrap a full blown web application in background and let you understand how IOC and Request handling are really working in Spring (Quarkus is another beast) Except for that, you can run parts of the Tapestry stack as well as full blown applications from Quarkus and Spring using the best in both worlds. We are running pretty big application on top of Tapestry for years in mix and match conzept - Plain tapestry pages for simple forms, Micro SPAs everywhere we need komplex User interactions. Quartz for cron, Resteasy for Rest. And we had to port some Tynamo Libraries on Jackarta, before Tynamo does. No problem at all. Conclusion: Tapestry is simple, stable, predictable and extensible. Just use it, extend and contribute back to community. Or just don't use it ... say farewell and thanks to the authors created and contributors who supported this project all these years and be happy with others. Roman Mertyn On 2026/05/12 17:07:51 Giulio Micali wrote: > Hi Volker, > I don't get if you are fooling me or what. you call 7 classes a "project", > when 85% or more of that is a copycat of your code ? > > I don't call it a project, I call it a demo, a contribution "already > forked, already died, nobody cares". > If you don't agree with this definition, i can understand: you haven't the > need to fork. > Do you really think that the author copied so much for a different reason > that he had no choice, except hoping that you will integrate the idea in a > module, where it belongs ? > > And yes, sarcasm again. After all,it's the more appropriate answer to > condescension. > > Because if you get a technical(o strategic, as you wish) advice and you > tell me "It's a bad idea, we don't want to taint our splendid framework > putting that ***** of spring in the frontline", that is a serious answer. > People will see it, and does their Math. > if you(Ben) quote the entire history of open source, licensing(remember, > 85%), no-time(10 years) ecc.., and you(you) suggest ME to continue > refreshing the copy/paste routine of YOUR code in another repo ? > > Then you must be kidding. Very professional. > And no thanks, I already had been there, putting a fork of your code in the > trashcan because at each version the internals changes(when it wasn't > javascript). > if YOU want, I'll send you the project privately, rewritten with feet, but > it works and has the right dependencies resolved for spring boot 3.3.5 and > jakarta in the pom. > Your effort will be only the gradle module and code restyle. > > Have fun > > > Il giorno mar 12 mag 2026 alle ore 11:32 Volker Lamp ha > scritto: > > > Hi Giulio, > > > > I think Ben's reply was actually quite thorough and good-faith — he > > explained the real constraints the project faces, outlined concrete > > ideas for improvement, and even invited further contributions. > > Summarizing it as "fork or die" doesn't do it justice. > > > > That said, your frustration is understandable, and the points you raised > > about the developer experience are welcome. (The aggressive/sarcastic > > tone isn't, though.) The javax/jakarta migration was painful for > > everyone, and Spring Boot-style bootstrapping — just adding a dependency > > and having things work — is what many find convenient. > > > > We're a small team of volunteers, and we genuinely can't do everything — > > but that also means contributions from people who have just gone through > > the pain of modernizing old code are especially valuable. You clearly > > have a good understanding of what's missing. You could contribute back > > to the community by taking "ownership" of tapestry-boot. Happy to > > include a reference to it on the Tapestry website. > > > > The door is open. > > > > Cheers > > > > Volker > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > -- > Giulio Micali > -- rm
