Since stacktraces are printed when a cause is present in MojoExecutionException,

log the error instead and throw an exception without a cause.

Maybe it's better to have 2 MojoExecutionExceptions: one that signals
a real error/failure in maven (or pom setup), and one that just
signals normal build errors (no stacktrace printed).


git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@291423 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Kenney Westerhof 2005-09-25 15:07:39 +00:00
parent 3f3d07908d
commit 9592dddc6e
1 changed files with 2 additions and 2 deletions

View File

@ -118,8 +118,8 @@ public class ForkMojo
if ( response.isExecutionFailure() )
{
throw new MojoExecutionException(
"Integration test failed" );
getLog().error( "Integration test failed", response.getException() );
throw new MojoExecutionException( "Integration test failed" );
}
}