[jira] [Commented] (MNG-6533) ProjectBuilder.build(list_of_projects,...) does not contain MavenProject in exception report

["Hudson (JIRA)" <ji...@apache.org>]

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

Hudson commented on MNG-6533:
-----------------------------

Build succeeded in Jenkins: Maven TLP » maven » MNG-6169/MNG-6550 #8

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6169%252FMNG-6550/8/

> ProjectBuilder.build(list_of_projects,...) does not contain MavenProject in exception report
> --------------------------------------------------------------------------------------------
>
>                 Key: MNG-6533
>                 URL: https://issues.apache.org/jira/browse/MNG-6533
>             Project: Maven
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.5.4, 3.6.0
>            Reporter: Mickael Istria
>            Assignee: Hervé Boutemy
>            Priority: Major
>             Fix For: 3.6.1
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> To save a lot of CPU and RAM in Eclipse m2e, we're trying to use {{ProjectBuilder.build(List<File> projects ...)}} instead of sequencing multiple {{Projectbuilder.build(File singleProject...)}}. This has a big positive impact on m2e.
> However, we noticed that when the operation is failing in some case because pom is incomplete (which is a pretty usual state in the IDE), the multi-projects method does not return the MavenProject in the {{ProjectBuildingException.getResults()}}, while the single-project method does.
> Adding MavenProject for the multi-project {{ProjectBuilder.build(...)}} would allow m2e to use this method and save ~75% RAM and CPU in many operations.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)