Sometimes our tests fails because seam model is not correct. For example we have:

@Name("comp1")
public class Comp1

Seam builder creates "comp1" component but getJavaDeclaration() return null even if the project is correct and all nedded libs are in classpath.
It's hard to reproduce this issue. We need to investigate it and found the resoun of this bug. Looks like thread racing is responsible for that.