Hi Felix, Felix Roethenbacher schrieb:
The reason why I deliberately left out the unit tests in the beginning was a dependency on a generic abstract test case. If migrated to Maven this code would have to be placed in a separate module. Dependent modules would have to declare a dependency on this module with scope 'test'.
for the moment, I have put the AbstractAccessControlTest and AbstractLenyaTestCase in the core-api module, which exports them as a test jar. But if I understand you correctly, this is not a recommended approach. Should we add a separate module for these classes?
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 most serious problems are caused by the URI handling; I have temporarily added the test publication as a resource in the core-impl module, so that the tests can at least be run. I had to patch the user management and the sourcerepository a bit to make them work with resource:// URIs. I'll continue to make the tests work later this evening.
-- 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]
