[MRELEASE-515] release:prepare eats the root cause of the exception

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta-9
• Fix Version/s: 2.0
• Flags: Patch
• Assignee: Brett Porter
• Reporter: Kohsuke Kawaguchi
• Created: 19/Jan/10 18:51
• Updated: 05/Apr/15 14:54
• Resolved: 26/Jan/10 09:01

Description

The PrepareReleaseMojo.execute() method contains the following statement:

try
{
    releaseManager.prepare( config, getReleaseEnvironment(), reactorProjects, resume, dryRun );
}
catch ( ReleaseExecutionException e )
{
    throw new MojoExecutionException( e.getMessage(), e );
}
catch ( ReleaseFailureException e )
{
    throw new MojoFailureException( e.getMessage() );
}

As you can see, the stack trace and nested exception of the ReleaseFailureException is lost, which makes it unnecessarily hard to diagnose the root cause of problems like MRELEASE-332. The code should be modified to something like:

throw (MojoFailureException)new MojoFailureException( e.getMessage() ).initCause(e);