[
https://issues.apache.org/jira/browse/MNG-5695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783116#comment-17783116
]
ASF GitHub Bot commented on MNG-5695:
-------------------------------------
hboutemy commented on PR #236:
URL:
https://github.com/apache/maven-plugin-tools/pull/236#issuecomment-1794214621
in MPLUGIN-204 we advised using `@Component` (that would use the trick to
transform to parameters in the plugin descriptor XML), but later we advised
back:
https://github.com/apache/maven-plugin-tools/commit/f8a946df81176cfdf4be2f37c04b881b961d6994
see https://issues.apache.org/jira/browse/MPLUGIN-257
> inconsistent custom Guice 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 ({{MavenSession}}) 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 ({{MavenProject}} and {{MojoExecution}}) works for
> components from maven plugins but not for maven core and core extensions.
> Need to consistently bind custom Guice scopes in all realms.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
