Hello All,
We had the same idea about adding a classifier or altering the maven
coordinates. What we found is that adding "-jakarata" to the artifact
names worked extremely well and required very minimal changes to the
Tapestry 5 gradle build. One benefit of this approach is that we were
able
houghts?
Best Regards,
David Taylor
On 2/13/2024 8:00 AM, Thiago H. de Paula Figueiredo wrote:
On Tue, Feb 13, 2024 at 8:20 AM Carlos Montero Canabal
wrote:
Good job Tapestry Team, congratulations!
Thanks!
I have a question. This release supports Java 21 but checking Tomcat
Hi Ben,
Have you considered using Graal Javascript in place of Rhino? It
implements the latest ECMAScript spec and also runs nicely on a plain
Java 8 VM with minimal dependencies. We have been using Graal for
advanced scripting features in our product and are very happy with the
fit and finis
Thanks Geoff. I hope you are doing well. Some crazy times.
David
On 4/15/2020 12:04 AM, JumpStart wrote:
Very good question. I’ll see if I can get it up again shortly.
Geoff
On 15 Apr 2020, at 12:02 pm, David Taylor wrote:
Hi!
Search Results
Web results
I noticed Geoff's Tap
Hi!
Search Results
Web results
I noticed Geoff's Tapestry Jumpstart site has been down for the last few
days. DNS is still resolving, but the server responds with a connection
timeout. Does anyone know what happened to the site?
Thanks,
David
stoppers?
Assuming there are no blocking issues, what is the next step forward
with 5.5?
Regards,
David
On 6/18/2019 8:46 AM, Thiago H. de Paula Figueiredo wrote:
On Thu, Jun 13, 2019 at 5:04 PM David Taylor
wrote:
Hello,
Hi!
Does anyone know where we stand on the Tapestry 5.5 release
Hello,
Does anyone know where we stand on the Tapestry 5.5 release? Are there
specific blocking issues that need to be addressed? I recall seeing one
related to Java 11 and ASM, but it is not clear if that is being worked
on at the moment.
We are working on upgrading our applications to Java
Anyone have experience working with the @extend directive in CSS
preprocessors?
I came across a post that advocates decoupling HTML markup from
bootstrap classes by using @extend. I don't particularly agree with many
of the points the author makes, but the technique is intriguing and
might be
I completely agree. We would like to move to bootstrap 4 and improve our
integration with Kendo UI in the process.
We also need to upgrade bootstrap 3 to the latest version since there
have been issues that cause it to show up as a XSS risk on application
vulnerability scans. Just yesterday bo
It would be great to see a fresh vision and roadmap for Tapestry going
forward. Tapestry has many strengths, but has a relatively steep
learning curve and does not do enough to help new developers get off the
ground. We have been using Tapestry for a very long time and still find
it challenging
We use JSW (last non-GPL version) + Jetty 9.3/Tomcat 8 + Tapestry 5.4 in
production on various flavors of Windows without issue. The only unusual
thing I have seen is a problem with HikariCP having problems locating
the jTDS driver at system startup. Very weird since the problem does not
occur
If Tapestry is so terrible, why waste all the energy? Just to be obnoxious?
We would abandon Tapestry tomorrow if it weren't so bloody fast and easy
to extend.
emailsig On 2/12/2016 3:53 PM, Thiago H de Paula Figueiredo wrote:
On Fri, 12 Feb 2016 17:19:28 -0200, Emmanuel Sowah
wrote:
Hi
me other components, e.g. in Label's "for" attribute). Use "id" when
you want to force some particular "id" value in the generated HTML, but
watch for cases when it is component that might be included multiple times
on a page, in loops or in AJAX responses.
Best r
Hello,
I am working on a custom component library and have observed some
unexpected behavior regarding attribute namespace prefix usage. Can
someone please clarify the official Tapestry rules regarding the usage
of component attribute namespace prefixes? Here are two scenarios that I
believe
14 matches
Mail list logo
