Hi Felix,
Felix Roethenbacher schrieb:
Andreas Hartmann wrote:
Andreas Hartmann schrieb:
[…]
Have you resolved the nested dependencies of the unit tests in the
various modules yet? Currently most unit test don't compile and
the ones which do are failing.
The ones in SVN should compile now, but they are still failing. I'm
resolving exception after exception which occur due to missing bean
wiring, which is to be expected – but I guess this will improve as
soon as the basic components are correctly wired.
The tests in SVN are now succeeding for me.
Not for me:
Missing:
----------
1) org.apache.lenya:lenya-core-impl:test-jar:tests:2.2.0-SNAPSHOT
[...]
Path to dependency:
1) org.apache.lenya:lenya-core-workflow:jar:2.2.0-SNAPSHOT
2) org.apache.lenya:lenya-core-impl:test-jar:tests:2.2.0-SNAPSHOT
sorry, this dependency was obsolete. I forgot to remove it, now it
should work.
Maybe you have to remove the Lenya artifacts from your local Maven
repository to see this.
Thanks for the hint – that way I also got the error.
I think you moved this to lenya-core-impl-tests
Actually I moved the abstract tests to the core-api module to avoid the
dependencies from the "peripherical" modules to the core-impl module.
The core-impl-test module is isolated.
but if I add
this dependency I get a cyclic dependencies error. The problem is that
the unit tests inherit from some abstract test classes which are
in the core modules, hence the cyclic dependency. Probably we
should simplify the test classes and get rid of these abstract
test classes.
I guess it's OK to have the abstract test classes in the core-api
module, since this one is needed by virtually all other modules. WDYT?
But of course I don't mind simplifying the tests; it would be nice if
one doesn't have to extend a proprietary abstract test class.
Thanks for your help!
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
