Access to Surefire test output

2010-09-14 Thread sebb
If a Surefire test fails, it's usually necessary to be able to read the file(s) in the surefire-reports directory to resolve the problem. However, the Gump mails don't seem to give access to this information, unless one adds a suitable report tag to the descriptor. This is very tedious to have to

Re: svn commit: r996958 - /gump/metadata/project/commons-proper.xml

2010-09-14 Thread Stefan Bodewig
On 2010-09-14, s...@apache.org wrote: -pom name=jci/pom.xml/ +pom name=../pom.xml/ Uhm, no. I've reverted that part. The commons-beanutils project has a home element that points at beanutils/dist - that's why the .. was needed - pom and jar are resolved relative to home. commons-jci

BATCH: All dressed up, with nowhere to go...

2010-09-14 Thread gump
Dear Gumpmeisters, The following 2 notifys should have been sent *** G U M P [g...@vmgump]: Project apacheds-server-integ-test (in module apacheds) failed [g...@vmgump]: Project activemq-jaas (in module activemq) failed

Re: svn commit: r996958 - /gump/metadata/project/commons-proper.xml

2010-09-14 Thread sebb
On 14 September 2010 18:49, Stefan Bodewig bode...@apache.org wrote: On 2010-09-14, s...@apache.org wrote: -    pom name=jci/pom.xml/ +    pom name=../pom.xml/ Uhm, no.  I've reverted that part. Sorry ... The commons-beanutils project has a home element that points at beanutils/dist -

Re: Access to Surefire test output

2010-09-14 Thread Stefan Bodewig
On 2010-09-14, sebb wrote: However, the Gump mails don't seem to give access to this information, unless one adds a suitable report tag to the descriptor. This is very tedious to have to do for every test. This is the same as having to add jar elements, isn't it? Indeed, perhaps there