"thomas.diesler(a)jboss.com" wrote : | What we do with the OSGi example and functional test is a specific solution to the general problem of Maven integration testing | | http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing | | Anyhow, the MC framework needs to work in AS and the OSGi examples must run in AS. This is not something you can do in an Eclipse unit test. | | I realize, that building the installer, installing the framework, starting the target container, running the examples against the target container is not a practical prerequisite for an SVN commit. | | However, everybody should at least be aware of the functionality that already works and is being tested. One click on the public hudson instance can pickup potential integration issues, which can then be looked at and fixed locally. | That's not what I'm saying. I mean why isn't this feature being properly unit tested in framework/reactor? The FrameworkTest lets you setup a "minimal" JBoss instance (without all the other JavaEE services - just the basic OSGi stuff). So it should be possible to write a unit test for something that is broken in the integration tests so it won't regress in future by a bad commit in framework/reactor. On the thirdparty library stuff. The integration tests should not be running off reactor/framework trunk. The version used there should only be updated when the AS and osgi framework agree about thirdparty dependencies. i.e. once the thirdparty stuff has been updated into the AS at the end of the latest changes (once they are stable). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266979#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...