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
Maybe you have to remove the Lenya artifacts from your local Maven
repository to see this.
I think you moved this to lenya-core-impl-tests 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.
- Felix
I created a directory $LENYA_HOME/pubs containing the test publication.
To make the tests run you have to update the paths in
pubs/test/config/access-control/access-control.xml.
To avoid cyclic dependencies, I created a separate module for the core
impl tests. This way, the core impl tests can depend on various modules
which have runtime dependencies to the core impl (that is, to the
service declarations).
So, the basic read/write operations to the repository are working again.
From my PoV the next steps would be:
- migrate the remaining tests
- make the webapp work again, incl. design of the directory structure etc.
Of course any help is greatly appreciated!
-- Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
