[ https://issues.apache.org/jira/browse/MPH-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16417972#comment-16417972 ]
Karl Heinz Marbaise commented on MPH-144: ----------------------------------------- [~michael-o] I know. Thats the reason why I thought about a supplemental parameter like {{mvn -q -Dstdout=true help:evaluate...}} to make it explicit to the user and only for help plugin...the question is on the other hand if we need something similar in other plugins (I'm not sure?)...but to handle the case running this from scripts and not to use other ugly things it might be a compromise which is reasonable.. > mvn help:evaluate -Dexpression=project.groupId Can't be used in scripts. > ------------------------------------------------------------------------ > > Key: MPH-144 > URL: https://issues.apache.org/jira/browse/MPH-144 > Project: Maven Help Plugin > Issue Type: New Feature > Reporter: Karl Heinz Marbaise > Priority: Minor > > Currently if you use {{mvn help:evaluate -Dexpression=project.groupId}} > there will be some lines generated with {{[INFO] ...]]}} If you use {{mvn > help:evaluate -Dexpression=project.groupId -q}} you won't get anything > printed out. > It would be a good idea to have an output via a supplemental parameter like > this: > {{mvn help:evaluate -Dexpression=project.groupId -Dstdout=true -q}} to get > printed out the information like this (: > {code} > 0.2.0-SNAPSHOT > {code} > this would give the opportunity to use the call within scripts etc. > Also might be possible in one go: > {{mvn help:evaluate -Dexpression=project.groupId -DoutputFile=result.txt -q}} > to write the expression result into a file. > Or the question is if it would be possible/good idea to print out the > resulting expression anyway (ignoring -q for only {{[INFO]...}} parts) > {{mvn help:evaluate -Dexpression=project.groupId -q}} -- This message was sent by Atlassian JIRA (v7.6.3#76005)