The XInclude spec does not forbid non local references. See https://www.w3.org/TR/xinclude/#include-location So it could definitely be something like: mvn:org.apache.maven:maven-snippet:1.0 Also, pointers are actually supported as shown by the unit tests [1].
That said, we did choose to only support relative URis (in [2]) and I'm sure it would be a good idea to open it to absolute URIs... [1] https://github.com/apache/maven-xinclude-extension/blob/main/src/test/java/org/apache/maven/xinclude/stax/XIncludeTest.java#L111-L117 [2] https://github.com/apache/maven-xinclude-extension/blob/main/src/main/java/org/apache/maven/xinclude/LocalXmlResolver.java Le jeu. 23 janv. 2025 à 12:55, Elliotte Rusty Harold <elh...@ibiblio.org> a écrit : > On Thu, Jan 23, 2025 at 12:16 AM Mark Derricutt <m...@talios.com> wrote: > > > > > If the xinclude support could use some form of GAV HREF, rather than > just a > > local file, that might cover the basic requirements/use cases (tho some > > users seem to make heavy use of plugin configuration merging over a > series > > of parents). > > XInclude is defined by the XInclude spec, not by Maven. You'd need to > define a completely different inclusion model or perhaps define a new > URI type for Maven GAV coordinates, then add support for this to the > XInclude engines. I'm also not sure what that might mean. Do you > really want to include an entire pom.xml? Probably not, and XPath > fragment identifiers aren't well understood or supported. > > > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > > -- ------------------------ Guillaume Nodet
