Jorg,
well that's weird, i just tested it again and it works now. Must have
done something stupid back then, leading me to the wrong conclusion.
Don't feel bad, I have embarrassed myself on the Maven list by asking a question about something not working, which later worked. But, maybe that doesn't make you feel any better :-)
So +1 for pulling up that resource element to the root pom :)
maven -Dmaven.test.failure.ignore=true install (looks like Maven-2.0.2 might include the capability to fork tests, which might alleviate this problem that Carsten also faced).
BTW, org.apache.avalon.fortress.impl.role.test.ServiceMetaManagerTestCase fails, will need to figure that one out.
Finally, I have commented out the invocations of maven-fortress-plugin (meta), because of a chicken and egg problem. Meta depend on fortress-container, but fortress container depends on a couple of components (sourceresolve, etc.) which depend on meta....need to figure this circular dependence with some m2 magic (activations, combined with properties, I guess).
Shash
