Fix MavenStaxReader location reporting for properties

[gnodet]

Problem

The location for properties (Map elements) in the MavenStaxReader was being captured after calling nextText(), which moves the parser position past the element. This resulted in incorrect location information being reported.

For example, when parsing:

<properties>
  <maven.compiler.source>17</maven.compiler.source>
</properties>

The location for maven.compiler.source would point to the position after the closing tag instead of at the opening tag.

Solution

This PR fixes the timing of location capture for properties by saving the line and column numbers before calling nextText() that moves the parser position.

Changes

Modified Files

1. src/mdo/reader-stax.vm

   • Fixed location capture timing for properties (Map elements)
   • Location is now captured before nextText() is called

2. impl/maven-support/src/test/java/org/apache/maven/model/v4/MavenStaxReaderTest.java

   • Added testLocationReportingForElements() - tests regular elements with specific line and column number assertions
   • Added testLocationReportingForAttributes() - tests XML attributes (root on project, child.scm.connection.inherit.append.path on scm)
   • Added testLocationReportingForListElements() - tests list elements (modules) with specific line and column number assertions

Testing

All tests pass successfully:

• ✅ 10 tests in MavenStaxReaderTest (including 3 new comprehensive location reporting tests)
• ✅ Location reporting now works correctly for all element types
• ✅ Tests verify exact line and column numbers for accurate location tracking
• ✅ Existing ProjectBuilderTest continues to pass

Benefits

• More accurate location information for error reporting
• Better debugging experience when working with Maven POMs
• Consistent location reporting across all element types

[gnodet]

💚 All backports created successfully

Status	Branch	Result
✅	maven-4.0.x

Questions ?

Please refer to the Backport tool documentation