Currently the Seam component scanning takes prohibitively long in development when scanning a large project. My project has several thousand java files of which <1% are Seam components. For a Tomcat deployment changing from explicitly specifying the components to using the Seam scanning increases the startup time from 25 seconds to 50 seconds. Most of the 25 seconds is building a hibernate session factory.
A possible enhancement would be to allow restriction of the packages that will be scanned via something in the components.xml.
Without this present behaviour is default. With it, it will only scan specified packages.
Current workaround would be to package into separate jars but that's not always possible esp in development.