Hey Toni, On Nov 21, 2009, at 18:31 , Toni Menzel wrote:
> This is actually "home made" by placing integration tests in the component > under test. > This way you create a chicken egg problem. The tests (executed before bundle > is being packaged, see maven lifecycle) grabs any older version of the > component it finds (matching the group+artifact+version) wich usually not > what you want to test. Good point, I wasn't aware of that. > Solution: put the integration tests into its own projects. Sounds nuts but > is just logical. Would have been nice if it was possible to run the tests after the bundle has been compiled, packaged and installed, but I'll move my integration tests to a separate project. We can also group all integration tests into one big integration test project, which saves us some pom.xml files, but might pose some restrictions as to the testing frameworks people want to use. > Also it would be good to upgrade to exam 1.2.0 (currently 0.6). I did that for the dependencymanager module, but did not want to do it for any of the other projects as I am not sure if everything should still work after a migration. Greetings, Marcel