[
https://jira.codehaus.org/browse/MINVOKER-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=334877#comment-334877
]
Karl Heinz Marbaise commented on MINVOKER-122:
----------------------------------------------
I aggree, but having the problem not only to test Maven 3.1+. But the problem
is how should i check the correct execution of plugins and callings/creation of
artifacts other than scanning the log output? Ok. Artifacts can be checked the
existence in target folder etc. But how to check expected warnings information
messages etc.
> Import information into groovy scripts of the running Maven environment
> ------------------------------------------------------------------------
>
> Key: MINVOKER-122
> URL: https://jira.codehaus.org/browse/MINVOKER-122
> Project: Maven Invoker Plugin
> Issue Type: New Feature
> Affects Versions: 1.5
> Reporter: Karl Heinz Marbaise
> Assignee: Anders Hammar
> Priority: Minor
>
> During the execution of a postbuild.groovy script i'm checking the contents
> of the build.log output (output of plugins etc.). The problem is that based
> on the differences between MVN 2.2.1 and MVN 3.0.? the output looks
> different. But inside a verify.groovy i don't know under which version of
> Maven the integration-tests has been run...so it's not simple to make a
> difference here...It might be a good idea to get this information inside the
> groovy script.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
