[ https://jira.codehaus.org/browse/MNG-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Fedorenko closed MNG-5695. ------------------------------- Resolution: Fixed Fix Version/s: 3.2.4 Should be fixed now main: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=b80fb7d7ce46c67cc2caa4e136430add83535e23 tests: https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=b80fb7d7ce46c67cc2caa4e136430add83535e23 > inconsistent custom scope bindings > ---------------------------------- > > Key: MNG-5695 > URL: https://jira.codehaus.org/browse/MNG-5695 > Project: Maven > Issue Type: Bug > Reporter: Igor Fedorenko > Assignee: Igor Fedorenko > Fix For: 3.2.4 > > > Session scope is only available for maven core and core extensions components > (i.e. -Dmaven.ext.class.path stuff), but does not work for components from > maven plugins. Mojo execution scope works for components from maven plugins > but not for maven core and core extensions. Need to consistently bind custom > scopes in all realms. -- This message was sent by Atlassian JIRA (v6.1.6#6162)