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

Posted to issues@maven.apache.org by "Guillaume Nodet (Jira)" <ji...@apache.org> on 2022/10/20 08:11:02 UTC

[jira] [Updated] (MNG-7182) Use a pull parser during the build/consumer transformation

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

Guillaume Nodet updated MNG-7182:
---------------------------------
    Fix Version/s: 4.0.0-alpha-2

> Use a pull parser during the build/consumer transformation
> ----------------------------------------------------------
>
>                 Key: MNG-7182
>                 URL: https://issues.apache.org/jira/browse/MNG-7182
>             Project: Maven
>          Issue Type: Improvement
>    Affects Versions: 4.0.0-alpha-1
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>            Priority: Major
>             Fix For: 4.0.0-alpha-1, 4.0.0-alpha-2, 4.0.0
>
>
> The new build/consumer POM introduced in Maven 4 is currently based on SAX parsing while the POM and other modello based resources are all parsed using the XPP3 StaX parser. This leads to the POM being parsed, transformed and serialised to string using SAX, then parsed again StaX. The performance penalty is quite big when having lots of projects in the reactor.
> This ticket aims at using a single step based on StaX parsers, allowing on-the-fly transformation / parsing in a single step, thus having nearly no performance drop compared to the current state.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)