I wiped it out and rechecked it out from source control; seems to be working
fine.
Thanks again.
On 11/15/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
I don't know why the changed file wasn't detected.
Start running mvn clean {your phase here} ie mvn clean package or mvn
clean test rather than mvn test directly and Maven will delete
target/* before running, which should take care of these kinds of
problems.
Wayne
On 11/15/06, Trevor Torrez <[EMAIL PROTECTED]> wrote:
> Thanks all; I do appreciate the help. The root cause was (of all
things) a
> space after the class name in hibernate.properties :-/
>
> Now I am back to why this was so hard to diagnose -- the tests, when run
> from maven (on the command line), is not picking up changes to that file
--
> but when the tests run in eclipse, the changes are reflected. Why is
that?
>
>
> On 11/15/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
> >
> > Check your Manifest.MF files and web.xml and other configuration files
to
> > make sure there's not a reference to the wrong version somewhere.
(Don't
> > just use the files in target; you'll need to crack open the packaged
> > JAR/WAR/EAR and all its JAR contents and look at all the config files
and
> > Manifests.)
> >
> > I had a situation recently where all my modules were set up to use the
> > log4j version specified by parent dependencyManagement node, but then
for
> > some reason my EAR module had a specific version declared, so that's
what
> > got bundled into the EAR, and then the Class-Path references in the
other
> > modules were incorrect.
> >
> > Just throwing out some ideas. No real clue why this is happening. You
> > might need to provide an <excludes> in the hibernate dependencies and
then
> > manually add ehcache as its own dependency with a specific version, as
> > suggested by Lee.
> >
> > Wayne
> >
> > On 11/15/06, Trevor Torrez <[EMAIL PROTECTED]> wrote:
> > > nope:
> > >
> > > $ grep -io 'ehcache[^ ]\+' maven.log
> > > ehcache:ehcache:1.2
> > > ehcache:ehcache:1.2.
> > > ehcache:ehcache:jar:1.2:compile
> > > ehcache\ehcache\1.2\ehcache-1.2.jar,
> > > ehcache\ehcache\1.2\ehcache-1.2.jar
> > > ehcache:ehcache:1.2
> > > ehcache:ehcache:1.2.
> > > ehcache:ehcache:jar:1.2:compile
> > > ehcache\ehcache\1.2\ehcache-1.2.jar,
> > > ehcache\ehcache\1.2\ehcache-1.2.jar
> > > ehcache:ehcache:1.2
> > > ehcache:ehcache:1.2.
> > > ehcache:ehcache:jar:1.2:compile
> > > ehcache\ehcache\1.2\ehcache-1.2.jar,
> > > ehcache:ehcache=net.sf.ehcache:ehcache:jar:1.2:compile,
> > > ehcache\ehcache\1.2\ehcache-1.2.jar
> > >
> > > other than the fact that hibernate is specifying org.ehcache, and
there
> > is a
> > > note that it has moved to net.sf.ehcache, nothing is odd about the
> > output
> > > that I can see. Changing the pom to explicitly pull net.sf.ehcache
> 1.2has
> > > no effect.
> > >
> > > There is also only one version reference to hibernate: 3.2.0.cr4
> > >
> > > Any other ideas?
> > >
> > > -t.
> > >
> > > On 11/15/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Run mvn -X and then grep the output for ehcache... You'll probably
see
> > > > a different version getting pulled in by another dependency
> > > > somewhere...
> > > >
> > > > Wayne
> > > >
> > > > On 11/14/06, Trevor Torrez <[EMAIL PROTECTED]> wrote:
> > > > > Ok; that almost makes sense; what, other than 'Quartz' should I
> > search
> > > > > nabble for? I cant find anything relevent.
> > > > >
> > > > > Answers to any of the following questions would also be
appreciated:
> > > > >
> > > > > How do i find out which of the dependencies is requesting the
bogus
> > > > > version? The only thing 'maven site' shows in the dependencies
is
> > > > > ehcache-1.2, the version that must be used with
hibernate-3. The
> > > > dependency
> > > > > graph shows that ehcache was required by hibernate-3, and no
other
> > > > > (dissimilar) reference to ehcache is on the page. I pulled out
> > explicit
> > > > > dependencies on hibernate from my project pom, and likewise the
only
> > > > > hibernate listed is 3.2.0.rc4 required by spring-hibernate3.
> > > > >
> > > > > Why is it a class not found exception for a class that is
obviously
> > > > there
> > > > > and correct and not a no-class-def error as would be expected
for a
> > > > bogus
> > > > > version of a dependency (wrong method invocation, exception in
> > > > initializer,
> > > > > etc)?
> > > > >
> > > > > Why is this error not showing up in eclipse, when as far as i
can
> > tell
> > > > the
> > > > > same jar files are being used.
> > > > >
> > > > > Thanks; much appreciated;
> > > > > -t.
> > > > >
> > > > > On 11/14/06, Lee Meador <[EMAIL PROTECTED]> wrote:
> > > > > >
> > > > > > This has been discussed before. You can find it in nabble, I
> > think.
> > > > > >
> > > > > > The issue has to do with spring wanting one version of
hibernate
> > and
> > > > > > hibernate wanting a version of ehcache and the versions
conflict
> > with
> > > > each
> > > > > > other. In my case, using Quartz which wanted another version
of
> > > > ehcache,
> > > > > > it
> > > > > > would pick one version of ehcache for one project and another
> > version
> > > > for
> > > > > > another project.
> > > > > >
> > > > > > You solve it by specifying versions for things in some places
and
> > > > > > excluding
> > > > > > dependencies in others. I forget the details.
> > > > > >
> > > > > > -- Lee
> > > > > > [snip]
> > > > > >
> > > > > > --
> > > > > > -- Lee Meador
> > > > > > Sent from gmail. My real email address is lee AT leemeador.com
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
