Al Sutton wrote:
** Out of date jars (newer versions may have bug fixes which would be useful) **
commons-io-1.3.2 (There is a 1.4, but I'm not sure of API compatibility).
http://commons.apache.org/io/upgradeto1_4.html says:
Compatibility with 1.3.2
Binary compatible
It was switched to codebehind in 2.1.3, that was the joy I had with the last
release series :).
Al.
--
* Written an Android App? - List it at http://andappstore.com/ *
==
Funky Android Limited is registered in England & Wales with the
company number 6741909. The registered head office is
On Tue, Jun 23, 2009 at 4:13 AM, Al Sutton wrote:
> A few things I've noticed (not hugely important, but may raise some end user
> questions);
>
> ** Upgrade issues **
>
> My project uses -codebehind-plugin, -core, -rest-plugin, -sitemesh-plugin.
> After the upgrading just the jars I get;
>
> Cau
Al Sutton wrote:
My project uses -codebehind-plugin, -core, -rest-plugin,
Doesn't REST depend on convention? I'd be wary of using codebehind
alongside convention/rest (plus codebehind is deprecated).
Dave
-
To unsubscribe,
Al,
Sitemesh 2.4.2 was released via the OpenSymphony maven repository.
So, this is an official release, but it was never announced on the
OpenSymphony site, but on Joe Walnes blog [1].
I did the maven repository push from the tagged sources for Sitemesh,
so this shouldn't require further explanati
A few things I've noticed (not hugely important, but may raise some end user
questions);
** Upgrade issues **
My project uses -codebehind-plugin, -core, -rest-plugin, -sitemesh-plugin.
After the upgrading just the jars I get;
Caused by: java.lang.ClassNotFoundException:
org.apache.struts2.res
