I also subscribe to the 'call is what it is' naming convention, but several package/class names are close to the win platform limit of 255. Although not broken, this leaves little room for output directory naming. For example:

org.jboss.jsr299.tck.tests.context.passivating.broken.enterpriseBeanWithNonPassivatingBeanConstructorParameterInInterceptor.EnterpriseBeanWithNonPassivatingBeanConstructorParameterInInterceptorTest.java

Produces under maven-surefire:

TEST-org.jboss.jsr299.tck.tests.context.passivating.broken.enterpriseBeanWithNonPassivatingBeanConstructorParameterInInterceptor.EnterpriseBeanWithNonPassivatingBeanConstructorParameterInInterceptorTest.xml

Adding a path like 'c:\\slave4\\openejb-trunk-win-sunjdk\\build\\tck\\cdi-embedded\\target\\surefire-reports\\junitreports
', which I in fact have no real control over as it is dictated by the buildbot, leads to failures due to invalid path names.

With some plugin directory name tweaking it is possible to work around the constraints. It would however be 'nice' to have a little more play in the naming scheme.

The current workaround on the buildbot (where path renaming is not an option) is to disable surefire report file creation using <useFile>false</useFile>.