How would I do the former? I have to specifically list jboss-seam-ui in my dependency section, and there's no compile-no-test scope. So far I've found no way to specifically exclude explicit dependencies.
For the latter, yes, but I'd prefer to be able to run tests before building WAR's for deployment too.
And, removing jboss-seam-ui doesn't seem to affect anything either... removing it doesn't help the Maven tests, and keeping it on the classpath when running tests through Eclipse doesn't cause them to fail either.
Do any of the example apps use Maven? If so, then I imagine you'd easily be able to replicate these problems and much more easily debug them.
Not currently, its a roadmap item.
Are you using a war for deployment or an ear?
Gah, yet another limitation of maven.
war.
By the way, in case you didn't see it, I commented on your Maven blog post with information about a Maven properties plugin.
So the problem is the ajax4jsf filter should not be installed in the test environment - excluding either the richfaces or seam ui jar will achieve this. How we best achieve this with Maven is another matter...
Why don't I have that problem when running the test from Eclipse though? All the jars are on the classpath...