I'm unsure whether this is a bug or an intended feature. I would expect that if I have a module, eg. seam-test that depends on a module seam-web, then the libraries defined in seam-web does not appear on the classpath of seam-test when running testNG from this module. If I need libraries from seam-web, I would check the "export" box in the dependency settings for seam-web. But I find that when running the tests, all libraries from seam-web are included on the classpath, which raises issues when using SeamTest and JBoss Embedded.