I have a question regarding this disabling live-service reloading since I'm
the one who still gets IllegalAccessErrors in my service when it calls
static package-private method in some other utility class:
Why is this disabling realized via JVM property and not deafult
configuration mechanism that can be hardcoded inside module class? I try
always to make my web apps work out-of-box just by droping WAR inside
deployment dir without configuring the environment (in this case I would
have to edit Tomcat startup scripts for this JVM property wherever I
deploy)?
Should I reopen/report this IllegalAccessError issue that was closed with
5.2.1, or no more development will be spend on this issue and JVM property
should be treated like workaround from now on?
-Vjeran
----- Original Message -----
From: "Howard" <hls...@gmail.com>
Newsgroups: gmane.comp.java.tapestry.user
To: <users@tapestry.apache.org>
Sent: Monday, November 01, 2010 9:01 PM
Subject: [Tapestry Central] Tapestry 5.2.2
... and the latest version of Tapestry, 5.2.2, is now available. This
is the second beta release for Tapestry 5.2, addressing a few bugs in
5.2.1, and adding a couple of minor non-disruptive improvements ...
read about it in the release notes.
Tapestry 5.2.2 is available for download, or via Maven:
<dependency> <groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-core</artifactId> <version>5.2.2</version>
</dependency>
I expect some minor issues will be addressed in Tapestry 5.2.3. Expect
that in a week or so.
--
Posted By Howard to Tapestry Central at 11/01/2010 01:01:00 PM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
