maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Closed: (MNG-4669) Adjust the expected message string in MavenITmng2690MojoLoadingErrorsTest
Date Fri, 07 May 2010 13:29:13 GMT


Benjamin Bentmann closed MNG-4669.

    Resolution: Fixed
      Assignee: Benjamin Bentmann

Applied in [r942067|]. Despite log scrapping
being generally very fragile, it's sometimes the only to verify user experience...

> Adjust the expected message string in MavenITmng2690MojoLoadingErrorsTest
> -------------------------------------------------------------------------
>                 Key: MNG-4669
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Wish
>          Components: Integration Tests
>    Affects Versions: 3.0-beta-1
>            Reporter: Stuart McCulloch
>            Assignee: Benjamin Bentmann
>            Priority: Minor
>         Attachments: MavenITmng2690MojoLoadingErrorsTest_Message.patch
> The current MavenITmng2690MojoLoadingErrorsTest expects the following message:
>   "(?i).*required class was missing during (mojo )?configuration.*"
> in the mvn output when executing a mojo with a field that has a missing class.
> This pattern does not quite match the error when running with Guice, because Guice detects
the missing class slightly earlier (before Maven configuration) while scanning the declared
fields for @Inject annotations.
> The following pattern matches both Plexus and Guice error messages:
>   "(?i).*required class (i|wa)s missing( during (mojo )?configuration)?.*"
> any chance the attached patch could be applied to the MavenITmng2690MojoLoadingErrorsTest?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message