You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Robert Scholte (JIRA)" <ji...@apache.org> on 2018/12/09 09:29:00 UTC

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

     [ https://issues.apache.org/jira/browse/MNG-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte reassigned MNG-6533:
-----------------------------------

    Assignee: Robert Scholte

> 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: Robert Scholte
>            Priority: Major
>             Fix For: 3.6.1
>
>
> 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 methods does not retrn 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)