You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2015/12/25 12:49:51 UTC
[jira] [Closed] (MECLIPSE-600) Exceptions thrown from catch blocks
in EclipsePlugin.writeAdditionalConfig() should include cause
[ https://issues.apache.org/jira/browse/MECLIPSE-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MECLIPSE-600.
-----------------------------------
Resolution: Won't Fix
Assignee: Robert Scholte
The Apache Maven team has decided to retire the maven-eclipse-plugin, so this issue won't be fixed.
> Exceptions thrown from catch blocks in EclipsePlugin.writeAdditionalConfig() should include cause
> -------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-600
> URL: https://issues.apache.org/jira/browse/MECLIPSE-600
> Project: Maven Eclipse Plugin (RETIRED)
> Issue Type: Improvement
> Affects Versions: 2.7
> Environment: N/A
> Reporter: Jordan Stewart
> Assignee: Robert Scholte
> Priority: Minor
> Attachments: include-cause.patch
>
>
> The {{MojoExecutionException}}s thrown from the catch blocks in EclipsePlugin.writeAdditionalConfig() do not include the caught exception.
> The error message displayed when this occurs indicates that the problem is with the target file, when in fact it may be a problem with the source file:-
> The particular problem I ran into was that the source file path was derived using a property which happened to be undefined (as I was setting up the project without reading the instructions, which said to add that property to my settings.xml config file . . .)
> Having the actual cause available would speed up resolution of problems like this.
> Patch attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)