That's clearly a limitation of XPP3 which is a minimal xml parser.
For simple use cases, it may be easier to rely on adding support for custom
XML entities, it should be much easier to support than xinclude.

Le mer. 17 nov. 2021 à 15:17, Romain Manni-Bucau <[email protected]> a
écrit :

> Hi all,
>
> Almost everything is in the subject: any reason our pom parser prevents to
> use XML includes (https://www.w3.org/TR/xinclude/)?
>
> It would be very convenient to import some part of pom definition from
> .mvn/ or a project folder (indeed remote/insecured imports would be
> forbidden).
>
> Just a xpp3 limitation or something deeper?
> Do we want to support it?
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <
> https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>


-- 
------------------------
Guillaume Nodet

Reply via email to