[
https://issues.apache.org/jira/browse/MNG-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17187304#comment-17187304
]
Falko Modler commented on MNG-6979:
-----------------------------------
Btw, I think that {{currentProject}} should be set in case
{{project.isExecutionRoot()}} is {{true}}.
This block is just a few lines below the line which [~gastaldi] has linked in
[the third
comment|https://issues.apache.org/jira/browse/MNG-6979?focusedCommentId=17184880&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17184880].
> MavenSession.getCurrentProject may return an incorrect project in a
> multimodule build
> -------------------------------------------------------------------------------------
>
> Key: MNG-6979
> URL: https://issues.apache.org/jira/browse/MNG-6979
> Project: Maven
> Issue Type: Bug
> Components: core
> Affects Versions: 3.6.3
> Reporter: George Gastaldi
> Priority: Major
> Attachments: project.zip
>
>
> Having an extension that just displays the current project, like in:
> {code:java}
> @Singleton
> @Named
> public class BuildModuleSelector extends AbstractMavenLifecycleParticipant {
> @Inject
> private Logger logger;
> @Override
> public void afterProjectsRead(MavenSession session) throws
> MavenExecutionException {
> logger.info(session.getCurrentProject().toString());
>
> session.setProjects(Collections.singletonList(session.getCurrentProject()));
> }
> }
> {code}
> Will fail to resolve the current project when executed in the root of a
> project that depends on a module with the same parent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
