[
https://jira.codehaus.org/browse/MNG-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=338115#comment-338115
]
Stephen Connolly commented on MNG-5530:
---------------------------------------
We cannot have a test that requires 3.1.2-SNAPSHOT when there is no such
version in central. It seems that the test assumes *version of maven that the
tests are being run with* instead, so the test case probably needs to filter
that version into the pom under test. Another alternative would be to switch to
3.2.0 once we actually cut that release as that would be a release version and
one presumes we will have to maintain backwards API compat for at least some
period of time
> mojo execution guice scope
> --------------------------
>
> Key: MNG-5530
> URL: https://jira.codehaus.org/browse/MNG-5530
> Project: Maven 2 & 3
> Issue Type: Improvement
> Affects Versions: 3.1.0
> Reporter: Igor Fedorenko
> Assignee: Igor Fedorenko
> Fix For: 3.2
>
>
> It'd be nice to have custom Guice scope
> (http://code.google.com/p/google-guice/wiki/Scopes) for each mojo execution.
> This would allow mojo execution configuration and related objects to be
> injected in regular JSR330 components.
--
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
