Comments from the peanut gallery… I often don’t understand Elliotte’s comments and suggestions but here, insofar as I understand what he’s talking about, I agree with him. I read through the patch and the discussion on the linked issue.
- trying to determine the model version from both the explicit model version and the namespace seems… nuts. - I haven’t used xml schemas for many years, but I thought you could specify the modelVersion element being at or near the top with the schema. Even if you don’t validate against the schema, you can reject poms with the element in the wrong place. - guillaume made several comments which I will distort and exaggerate as, in the brave new world of namespace 4.1.0 we will have a clean sweep and can fix all the xml problems… later. However, I don’t see any evidence that changing the namespace will have any effect on fixing the xml problems and as Elliotte says changing the namespace will undoubtedly cause problems. Namespace != schema version If anyone has time, I’d appreciate a simple example of why xpath doesn’t work on poms today. Many thanks, David Jencks Sent from my iPhone > On Mar 14, 2026, at 2:27 PM, Elliotte Rusty Harold <[email protected]> wrote: > > On Sat, Mar 14, 2026 at 1:08 PM Sylwester Lachiewicz > <[email protected]> wrote: >> >> Hi, >> >> So that means the <project><modelVersion> element indicates which >> XSD/schema version to use and we have different XSD files >> (maven-4.0.0.xsd, maven-4.1.0.xsd, etc.) where schema location would >> point to. >> Is that correct or do you mean something different ? Could You open PR >> with proposed changes so we all can be on the same page? > > I feel like I've done that before. I know I started a PR. Possibly I > didn't get around to completing it. Nope, here it is: > > https://github.com/apache/maven/pull/10952 > > Might not be finished yet. At the least, conflicts need to be > resolved, I can take another whack at it. > > -- > Elliotte Rusty Harold > [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
