You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2020/12/08 19:18:00 UTC
[jira] [Commented] (MNG-6979) MavenSession.getCurrentProject may
return an incorrect project in a multimodule build
[ https://issues.apache.org/jira/browse/MNG-6979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246098#comment-17246098 ]
Michael Osipov commented on MNG-6979:
-------------------------------------
I wll have a look at this again...this year.
> 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
> Assignee: Michael Osipov
> 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)