[
https://issues.apache.org/jira/browse/MSHARED-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036367#comment-16036367
]
Hudson commented on MSHARED-638:
--------------------------------
SUCCESS: Integrated in Jenkins build maven-shared #3732 (See
[https://builds.apache.org/job/maven-shared/3732/])
[MSHARED-638] use script description instead of hardcoded "script" in messages
(hboutemy: [http://svn.apache.org/viewvc/?view=rev&rev=1797598])
* (edit)
maven-script-interpreter/src/main/java/org/apache/maven/shared/scriptinterpreter/ScriptRunner.java
> use script description instead of hardcoded "script" in messages
> ----------------------------------------------------------------
>
> Key: MSHARED-638
> URL: https://issues.apache.org/jira/browse/MSHARED-638
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-script-interpreter
> Affects Versions: maven-script-interpreter-1.1
> Reporter: Hervé Boutemy
> Assignee: Hervé Boutemy
> Fix For: maven-script-interpreter-1.2
>
>
> examples:
> {noformat}[DEBUG] no script found in directory: ...
> [DEBUG] no script found in directory: ...{noformat}
> would be clearer written as:
> {noformat}[DEBUG] selector script: no script 'selector' found in directory ...
> [DEBUG] pre-build script: no script 'prepare' found in directory ...{noformat}
> or instead of:
> {noformat}[INFO] run script verify.bsh{noformat}
> having
> {noformat}[INFO] run post-build script verify.bsh{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
