Wendy,
Thanks for the reply. I was able to make it work with the following:
<dependency>
<groupId>net.sf.ehcache</groupId>
<artifactId>ehcache</artifactId>
<version>1.2</version>
<scope>compile</scope>
<exclusions>
<exclusion>
<groupId>ehcache</groupId>
<artifactId>ehcache</artifactId>
</exclusion>
</exclusions>
</dependency>
But I still have a question here -- I noticed that in the exclusion,
there's no "version" element allowed. I happened to benefit here from
the fact that ehcache had actually been moved to net.sf.ehcache, so I
used that as the dependency groupId. But I don't quite understand this
-- what I am trying to exclude is not ehcache, but a particular version
of it. Why isn't a version supported for the exclusion?
Brad
Wendy Smoak wrote:
On 7/2/06, Brad O'Hearne <[EMAIL PROTECTED]> wrote:
I have manually gone in and nuked the contents of target, and rebuilt /
packaged the WAR. I still get both jars -- I sent another email with the
details of this.
Examine the output of 'mvn package -X' to see if you can figure out
where each jar is coming from.
Take a look at mvn help:effective-pom to see if both dependencies are
in there.
Look at the poms and artifacts on ibiblio... and:
http://www.ibiblio.org/maven2/ehcache/ehcache/1.2/ehcache-1.2.pom
Ehcache 1.2 has been relocated to a different groupId,
'net.sf.ehcache' while ehcache 1.1 has not.
Double check that issue that Stephen linked to, but I still think you
need to <exclude> ehcache:ehcache from your hibernate dependency, then
declare the newer one. And use the correct groupId now that we know
what it is.
If that *still* doesn't work, use mvn archetype:create to set up a
project, and modify the pom so that it reproduces the problem, then
let us take a look at that.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
