[
https://issues.apache.org/jira/browse/MSHARED-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163106#comment-17163106
]
Hudson commented on MSHARED-910:
--------------------------------
Build succeeded in Jenkins: Maven TLP » maven-script-interpreter » master #53
See
https://builds.apache.org/job/maven-box/job/maven-script-interpreter/job/master/53/
> Redundant option failOnException
> --------------------------------
>
> Key: MSHARED-910
> URL: https://issues.apache.org/jira/browse/MSHARED-910
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-script-interpreter
> Reporter: Slawomir Jaranowski
> Assignee: Sylwester Lachiewicz
> Priority: Major
> Fix For: maven-script-interpreter-1.3
>
>
> In code of {{ScriptRunner}} we have:
> {code:java}
> if ( failOnException )
> {
> throw new RunFailureException( "The " + scriptDescription + " did not
> succeed. " + msg, stage );
> }
> else
> {
> throw new RunErrorException( "The " + scriptDescription + " did not
> succeed. " + msg, stage, t );
> }
> {code}
> This cause to only throw different exception, but in client code we should
> catch exception regardless of this option.
> I think that this complicate code of this class and code on client with
> process many exceptions.
> My proposition:
> - remove option {{failOnException}}
> - remove exceptions: {{RunFailureException}} and {{RunErrorException}}
> - throw by methods run, executeRun - {{ScriptEvaluationException}}
> I can do it - after your approval.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
