maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (MNG-6533),...) does not contain MavenProject in exception report
Date Thu, 29 Nov 2018 17:35:00 GMT


ASF GitHub Bot commented on MNG-6533:

mickaelistria opened a new pull request #197: [MNG-6533] Test: ProjectBuildingException miss
reference to MavenProject
   Following this checklist to help us incorporate your 
   contribution quickly and easily:
    - [x] Make sure there is a [JIRA issue]( filed

          for the change (usually before you start working on it).  Trivial changes like typos
do not 
          require a JIRA issue.  Your pull request should address just this issue, without

          pulling in other changes.
    - [x] Each commit in the pull request should have a meaningful subject line and body.
    - [x] Format the pull request title like `[MNG-XXX] - Fixes bug in ApproximateQuantiles`,
          where you replace `MNG-XXX` with the appropriate JIRA issue. Best practice
          is to use the JIRA issue title in the pull request title and in the first line of
          commit message.
    - [x] Write a pull request description that is detailed enough to understand what the
pull request does, how, and why.
    - [x] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will

          be performed on your pull request automatically.
    - [ ] You have run the [Core IT][core-its] successfully.
   If your pull request is about ~20 lines of code you don't need to sign an
   [Individual Contributor License Agreement]( if
you are unsure
   please ask on the developers list.
   To make clear that you license your contribution under 
   the [Apache License Version 2.0, January 2004](
   you have to acknowledge this by using the following check-box.
    - [x] I hereby declare this contribution to be licenced under the [Apache License Version
2.0, January 2004](
    - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

>,...) does not contain MavenProject in exception
> --------------------------------------------------------------------------------------------
>                 Key: MNG-6533
>                 URL:
>             Project: Maven
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.5.4, 3.6.0
>            Reporter: Mickael Istria
>            Priority: Major
> To save a lot of CPU and RAM in Eclipse m2e, we're trying to use<File>
projects ...) instead of sequencing multiple 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
> Adding MavenProject for the multi-project would allow m2e to
use this method and save ~75% RAM and CPU in many operations.

This message was sent by Atlassian JIRA

View raw message