[
https://issues.apache.org/jira/browse/MNG-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-5695:
-------------------------------
Description:
- 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.
- MavenProject and MojoExecution scope works for components from maven plugins
but not for maven core and core extensions.
Need to consistently bind custom scopes in all realms.
was: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.
> inconsistent custom scope bindings
> ----------------------------------
>
> Key: MNG-5695
> URL: https://issues.apache.org/jira/browse/MNG-5695
> Project: Maven
> Issue Type: Bug
> Reporter: Igor Fedorenko
> Assignee: igorfie
> Priority: Major
> Fix For: 3.2.5
>
>
> - 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.
> - MavenProject and MojoExecution 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
(v8.20.10#820010)
