Maven has this really weird concept of "closer" and "further" dependencies.
If the transitive dependency chain is shorter to 1.2.3, then that will be
used even if a dependency deeper in the chain asks for a newer version.
Hence when you move the ehcache dependency to the top level, all works
fine...
Mike.
On 5/31/07, Matt Raible <[EMAIL PROTECTED]> wrote:
To fix this problem, add the following to your pom.xml's dependencies:
<dependency>
<groupId>net.sf.ehcache</groupId>
<artifactId>ehcache</artifactId>
<version>${ehcache.version}</version>
</dependency>
And the following to your properties section:
<ehcache.version>1.3.0-beta2</ehcache.version>
Maven resolves dependencies based on the shortest path, so somewhere
Hibernate's dependency on 1.2.3 is overriding AppFuse's dependency on
1.3.0-beta2. Hopefully we'll fix this in 2.0 RC1 b/c EhCache 1.3.0 is
out. I think this bug is caused because Maven doesn't know that
1.3.0-beta2 is newer than 1.2.3 (yeah, it's messed up).
Matt
On 5/31/07, Azarias Tomás <[EMAIL PROTECTED]> wrote:
>
> ehcache-1.2.3
>
>
>
> mraible wrote:
> >
> > If you do "mvn package" on your project, which version of EhCache do
> > you end up with in your WEB-INF/lib directory?
> >
> > Your problem may be related to the following issue:
> >
> > http://issues.appfuse.org/browse/APF-777
> >
> > Matt
> >
> > On 5/31/07, Azarias Tomás <[EMAIL PROTECTED]> wrote:
> >>
> >> In the demo site it's OK.
> >> Mat u a right, I was having the same problem but I disable the
> >> gzipFilter,
> >> Now it's OK!
> >>
> >>
> >> mraible wrote:
> >> >
> >> > There should be nothing different as far as form handling. Have you
> >> > made sure your database supports UTF-8? There may be differences
when
> >> > rendering characters - I've seen that caused by different versions
of
> >> > the gzipFilter.
> >> >
> >> > Does it happen on the demo site too?
> >> >
> >> > http://demo.appfuse.org
> >> >
> >> > Matt
> >> >
> >> > On 5/31/07, Fan <[EMAIL PROTECTED]> wrote:
> >> >>
> >> >> I had tried using Appfuse 2.0-mX before Appfuse2.0-m5. The
previous
> >> >> version
> >> >> of appfuse 2.0 seems like no problem with UTF8 character. But when
I
> >> use
> >> >> Appfuse2.0-m5 on the same MySql database as I used for previous
> >> version,
> >> >> the
> >> >> UTF8 character does not show correctly, all showing "????"
> >> >>
> >> >>
> >> >> What missed out in the Appfuse2.0-m5 from the previous version ?
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
http://www.nabble.com/Appfuse-2.0-m5-does-not-support-UTF8---tf3847241s2369.html#a10896381
> >> >> Sent from the AppFuse - User mailing list archive at Nabble.com.
> >> >>
> >> >>
---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > http://raibledesigns.com
> >> >
> >> >
---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> > For additional commands, e-mail: [EMAIL PROTECTED]
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >>
http://www.nabble.com/Appfuse-2.0-m5-does-not-support-UTF8---tf3847241s2369.html#a10900490
> >> Sent from the AppFuse - User mailing list archive at Nabble.com.
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> >
> > --
> > http://raibledesigns.com
> >
> >
>
> --
> View this message in context:
http://www.nabble.com/Appfuse-2.0-m5-does-not-support-UTF8---tf3847241s2369.html#a10900670
> Sent from the AppFuse - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
http://raibledesigns.com
