On Mon, Jun 7, 2021 at 2:11 PM Guillaume Nodet <[email protected]> wrote:
> > There are current issues in our pom.xml parsing, particularly around > > namespaces, that aren't going to be resolved until we get rid of or > > fix Modello, and possibly that's going to require fixing XPP3. I don't > > know. However the XML parser should be an implementation detail. > > > > Which parsing problems exactly ? I used the MXParser / XPP3 for the Camel > reader and it has full support for namespaces afaik. > It's been a few months (or a year?) since I dug into this. Might just be Modello, not XPP3; I'm no longer sure. The fundamental mistake is that Maven allows pom.xml both with and without namespace declarations, and possibly does not properly handle prefixed element names. (It's been a little while so I might not remember every detail.) Either way, this misunderstanding makes it extremely difficult to process pom.xml files with standard XML tools such as XSLT and XQuery. This cost me a lot of extra work circa 2019/2020 when I was writing tooling that needed to process pom.xml files to follow dependency chains. At one point I dug into the code to see how hard it would be to repair this and let Maven work with XML namespaces instead of against them. Most of the offending code proved to be in plexus rather than maven itself, and it was made far more opaque by the multiple extra levels of indirection in the various frameworks like Modello that Maven sits on top of. -- Elliotte Rusty Harold [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
