Mike Perham wrote:
I found the problem. It had nothing to do with maven and everything to
do with the VM's incompetent error reporting. The problem was that the
DateLiteralBean class below linked to classes in jarA which linked to
classes in jarB. JarB was not in the classpath.
2750 [main]
From: Mike Perham
Sent: Saturday, September 24, 2005 11:07 AM
To: Maven Users List
Subject: [m2b1] tests not seeing classes?
I have a project which is compiling some Hibernate beans into
target/classes and then running an integration test with Derby to ensure
that the database creation and s
t: Re: [m2b1] tests not seeing classes?
On Sat, 2005-09-24 at 11:07 -0500, Mike Perham wrote:
> I have a project which is compiling some Hibernate beans into
> target/classes and then running an integration test with Derby to
> ensure that the database creation and simple queries work, e
On Sat, 2005-09-24 at 11:07 -0500, Mike Perham wrote:
> I have a project which is compiling some Hibernate beans into
> target/classes and then running an integration test with Derby to ensure
> that the database creation and simple queries work, etc.
Are these generated classes? I don't use hiber
I have a project which is compiling some Hibernate beans into
target/classes and then running an integration test with Derby to ensure
that the database creation and simple queries work, etc.
2750 [main] ERROR net.sf.hibernate.proxy.LazyInitializer - CGLIB
Enhancement failed
java.lang.NoClassDefF
