Hi Gregory >Are you running into this with anything else than when writing tests for >your ModuleVersionHandler ? If you extend >info.magnolia.module.ModuleVersionHandlerTestCase, you can override the >getModuleDescriptorPathsForTests method, so you tell >the test "framework" which modules to load, and discovery shouldn't be >needed. > >Ideally, such a test should not depend on other modules being installed. >Sometimes, it's inevitable, but if you're far down the list of >dependencies, and you get the whole installation process going on, your >tests are going to be very slow. Consider moving to >integration tests... but that is another debate. >
Thanks for this info. I have the problem while doing some tests on mocked contents which are loaded from properties files. So the module version handler test might probably not be the right base for extending. I'm currently happy with the previous hint about the surefire 'useManifestOnlyJar' configuration, which of course fails in windows-env, but works fine everywhere else. The module test cases also rely on dependencies on other modules which need to be loaded, so the manifest-only jar doesn't work for me. Best Regards, Marco -- 15 Years of Excellence: http://nca.me/15 ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
