Found a solution, upgrading to 3.0.0.M4 removes the use of the conflicting antlr class.
You may need to do some creative maven excludes of antlr depending on what other deps you use (hibernate in my case)
"The only issue I came across is that T5.1 and Spring 3 are using two
incompatible versions of Antlr library"
Is there a workaround? Pages will not load after startup due to this.
Excluding one or the other antlr deps will cause an error in either Tapestry or Spring.
Lubor Gajda wrote:
Hi Geoffrey,
I've tried T5.1.0.5 in combination with Spring 3.0.0.M3 and it works fine
for me. The only issue I came across is that T5.1 and Spring 3 are using two
incompatible versions of Antlr library, but injection of spring beans works
fine for me.
Could you please send us more information about your runtime environment
(e.g. list of jars on your classpath, your web.xml configuration, what
application server you are using, etc.)?
Thanks,
Lubor
On Mon, Jun 29, 2009 at 2:48 PM, Geoffrey Wiseman <
geoffrey.wiseman@gmail.com> wrote:
> On Mon, Jun 29, 2009 at 9:42 AM, Thiago H. de Paula Figueiredo <
> thiagohp@gmail.com> wrote:
>
> > Was it already released? Is it backward-compatible with Spring 1 and 2?
> >
>
> Spring 3.0 is up to Milestone 3.X; I gather a release candidate is due in
> the near future, so it might be a good time to start looking at it if T5.1
> wants to be compatible at the time of release.
>
> - Geoffrey
> --
> Geoffrey Wiseman
>
http://www.geoffreywiseman.ca/>
