You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2014/01/06 13:15:45 UTC

[jira] (MNG-5530) mojo execution guice scope

     [ https://jira.codehaus.org/browse/MNG-5530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Connolly reopened MNG-5530:
-----------------------------------


Integration test as committed fails when maven is any version other than 3.1.2-SNAPSHOT, e.g. see https://builds.apache.org/job/core-integration-testing-maven-3-jdk-1.7/933/

I have committed a temp workaround that should fix things but a better test is required
                
> 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