If you add it as a new dependency, it should override the version from
AppFuse. In an ideal world, you could specify an ehcache.version
property in pom.xml. Unfortunately, Maven doesn't allow overriding
properties in dependencies - except when you use -D or MAVEN_OPTS.
Matt
On 3/19/07, viggo <[
hmm, where do I change the version of EhCache used? It's not defined in any
of my pom.xml.
mraible wrote:
>
> This is caused by an issue with EhCache. It's fixed in 1.3.0-beta.
> We'll be upgrading AppFuse to 1.3.0 when it's released (est. 2 weeks).
>
> Matt
>
> On 3/18/07, viggo <[EMAIL PR
Thanks Matt, I will use the beta until the final release.
mraible wrote:
>
> This is caused by an issue with EhCache. It's fixed in 1.3.0-beta.
> We'll be upgrading AppFuse to 1.3.0 when it's released (est. 2 weeks).
>
> Matt
>
> On 3/18/07, viggo <[EMAIL PROTECTED]> wrote:
>>
>> I have a sp
This is caused by an issue with EhCache. It's fixed in 1.3.0-beta.
We'll be upgrading AppFuse to 1.3.0 when it's released (est. 2 weeks).
Matt
On 3/18/07, viggo <[EMAIL PROTECTED]> wrote:
I have a spring modular project (2.0-m4-SNAPSHOT), and when I run mvn install
on the core module the log
I have a spring modular project (2.0-m4-SNAPSHOT), and when I run mvn install
on the core module the log shows me this:
[lpoints] ERROR [Thread-2] DisposableBeanAdapter.destroy(148) | Couldn't
invoke destroy method of bean with name 'sessionFactory'
java.lang.IllegalStateException: Shutdown in pro
