You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/01/26 23:17:02 UTC

[jira] [Commented] (MNG-6638) Prevent reparsing POMs in MavenMetadataSource

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

Hudson commented on MNG-6638:
-----------------------------

Build succeeded in Jenkins: Maven TLP » maven » MNG-6071 #33

See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6071/33/

> Prevent reparsing POMs in MavenMetadataSource
> ---------------------------------------------
>
>                 Key: MNG-6638
>                 URL: https://issues.apache.org/jira/browse/MNG-6638
>             Project: Maven
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 3.5.4, 3.6.0, 3.6.1
>            Reporter: Stefan Oehme
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 3.6.2
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> MavenMetadataSource parses POM files even when an artifact comes from a project that is part of the current reactor build. This wastes a lot of time and memory, since the POMs of these projects are already in memory. It should instead try to find an existing project model in the reactor before falling back to POM parsing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)