You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mickael Istria (JIRA)" <ji...@apache.org> on 2018/11/27 14:53:00 UTC

[jira] [Created] (MNG-6529) ProjectBuilder.build(List projects, boolean, ProjectBuildingRequest) doesn't honor ProjectBuildingRequest.isResolveDependencies()

Mickael Istria created MNG-6529:
-----------------------------------

             Summary: ProjectBuilder.build(List<File> projects, boolean, ProjectBuildingRequest) doesn't honor ProjectBuildingRequest.isResolveDependencies()
                 Key: MNG-6529
                 URL: https://issues.apache.org/jira/browse/MNG-6529
             Project: Maven
          Issue Type: Bug
          Components: core
    Affects Versions: 3.5.3
            Reporter: Mickael Istria


I'm willing to upfate Eclipse m2e to take advantage of the `ProjectBuilder.build(List<File> project, boolean, ProjectBuildingRequest)` in Eclipse m2e to avoid duplication of MavenProject in the IDE in place of `ProjectBuilder.build(File singleFile, ProjectBuildingRequest)`. It's already measured to have drastically good impact on the IDE, as explained in [https://bugs.eclipse.org/bugs/show_bug.cgi?id=515668#c20] and [https://bugs.eclipse.org/bugs/show_bug.cgi?id=515668#c38].
However, using this cause regressions because the multi-projects entry-point method seems to totally ignore the `ProjectBuildRequest.isResolveDependencies()` flag and never returns a valid list of `MavenProject.getArtifacts()`.



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