You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (Jira)" <ji...@apache.org> on 2023/11/05 20:08:00 UTC

[jira] [Commented] (MPLUGIN-204) recognize classical Maven objects as components

    [ https://issues.apache.org/jira/browse/MPLUGIN-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783039#comment-17783039 ] 

Herve Boutemy commented on MPLUGIN-204:
---------------------------------------

notice that with MNG-5695 in Maven 3.2.5, ${session}, ${project} and ${mojoExecution} don't need that magic: they are supported as Guice scoped components

> recognize classical Maven objects as components
> -----------------------------------------------
>
>                 Key: MPLUGIN-204
>                 URL: https://issues.apache.org/jira/browse/MPLUGIN-204
>             Project: Maven Plugin Tools
>          Issue Type: New Feature
>    Affects Versions: 2.9
>            Reporter: Herve Boutemy
>            Assignee: Herve Boutemy
>            Priority: Major
>             Fix For: 3.0
>
>
> $\{session}, $\{project}, $\{mojo}, $\{plugin}, $\{settings} expressions are classical Maven objects injected into Mojos with readonly attribute (ie not configurable)
> As [discussed on the dev list|http://markmail.org/message/fruuocvtrhmkbo3y], having them automatically injected with @component annotation, recognized by their type, would simplify code



--
This message was sent by Atlassian Jira
(v8.20.10#820010)