maybe we should move the syntax thread to a new maven 4.2/5 desired feature one since it is unlikely it happens in 4.0.0 now?
side note: g:a:v is almost standardized using resolver API (even with classifier/extension-type) so for maven users it wouldnt be worse than splitting in attributes IMHO Romain Manni-Bucau @rmannibucau <https://x.com/rmannibucau> | .NET Blog <https://dotnetbirdie.github.io/> | Blog <https://rmannibucau.github.io/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/en-us/product/java-ee-8-high-performance-9781788473064> Javaccino founder (Java/.NET service - contact via linkedin) Le mar. 31 mars 2026 à 18:02, <[email protected]> a écrit : > Tangent from an end user: > > On Sat, Mar 28, 2026 at 06:04:24PM +0000, Fabrice Bauzac wrote: > > You can change parts of the structure indeed, e.g. instead of > > > > #+begin_src xml > > <dependency> > > <groupId>g</groupId> > > <artifactId>a</artifactId> > > <version>v</version> > > </dependency> > > #+end_src > > > > have > > > > #+begin_src xml > > <dependency>g:a:v</dependency> > > #+end_src > > > > Which is fine. But please note that doing so does not require a > > change of namespace. > > Please, no. Use XML as it was designed: > > <dependency groupId='g' artifactId='a' version='v'/> > > If making a clean break, there are lots of places where the POM schema > can be made more precise without introducing additional layers of > parsing. > > -- > Mark H. Wood > Lead Technology Analyst > > University Library > Indiana University Indianapolis > 755 W. Michigan Street > Indianapolis, IN 46202 > 317-274-0749 > library.indianapolis.iu.edu > > ORCiD: 0000-0002-9558-3768 >
