Closed GoogleCodeExporter closed 9 years ago
Shouldn't be. Some tests depend on easymock and it's listed in the
dependencies in that release, but I'd not expect that to be in the path here.
Is there a simple test which demonstrates the issue?
Original comment by ingen...@gmail.com
on 27 Dec 2011 at 9:58
It was not running in test environment. Just deployed and ran as jetty
webApp. No easymock jar(s) included in the war lib path. easy mock is a
test scope jar and was not packaged in by mvn. If it is included in the lib
path there's no that exception.
with easymock or not?
dependencies in that release, but I'd not expect that to be in the path
here. Is there a simple test which demonstrates the issue?
Original comment by metas.w...@gmail.com
on 4 Jan 2012 at 2:05
Original issue reported on code.google.com by
metas.w...@gmail.com
on 14 Dec 2011 at 8:24