[
https://issues.apache.org/jira/browse/MNG-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895835#comment-15895835
]
Christian Schulte commented on MNG-6173:
----------------------------------------
Thank you very much. There is [a
discussion|http://www.mail-archive.com/dev@maven.apache.org/msg112962.html]
ongoing on dev@. I'll paste the relevant part here so that things can be
discussed here.
bq. Hervé BOUTEMY Sat, 04 Mar 2017 09:55:27 -0800 I have one question, which
is recurring for every issue: what is the impact? I understand the logic: it
should fix a bug (that is told introduced in Maven 3.3.1), and the bug is
explained by the logic behind the javadoc. But no pointer to any code using
this method, and that shows that Maven 3.3.1 does not work any more, when
previous version were ok. Then what is explained here as a bugfix could cause
issues for others. I'm -1 unless I have some details on the impact. Regards,
Hervé
> MavenSession.getAllProjects() should return all projects in the reactor
> -----------------------------------------------------------------------
>
> Key: MNG-6173
> URL: https://issues.apache.org/jira/browse/MNG-6173
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.3.1, 3.3.3, 3.3.9
> Reporter: Christoph Böhme
>
> According to MNG-5582 {{MavenSession.getAllProjects()}} should return all
> projects in the reactor even if the set is constrained by {{--projects}}. The
> current implementation, however, returns the same constrained list that is
> returned by {{MavenSession.getProjects()}}.
> This bug seems to have been introduced when MNG-5775 was implemented.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
