AmarGhugare opened a new pull request, #13996:
URL: https://github.com/apache/maven/pull/13996

   The settings argument tokenizer drops explicitly quoted empty arguments: 
`first "" third` and `first '' third` both become two arguments. Inline 
`<options>` and `<alias>` content therefore differs from the equivalent 
structured `<arg/>` form, which already preserves the empty argument.
   
   Track whether a token has started independently of the output buffer's 
length. This keeps quoted empty arguments while preserving adjacent fragments, 
escaping, whitespace handling, and unclosed-quote errors. Update the tokenizer 
documentation and have the CLI forwarding class refer to the canonical 
implementation. No changes to JVM configuration parsing or shell launchers.
   
   Added 10 tokenizer tests and four settings-reader tests, including 
inline/structured equivalence and XML round trips. Nine cases failed before the 
fix.
   
   Validation on JDK 17 with Maven 3.10.0:
   
   ```text
   mvn -B -ntp -pl :maven-support -am verify
   ```
   
   All 12 selected reactor modules passed, including 24 support-module tests, 
Checkstyle, Spotless, RAT, model generation, and packaging. A separate focused 
check compiled the changed tokenizer and ran 43 tests, including all 29 
existing CLI tokenizer and mixed-content parsing tests; all passed. The full 
CLI module build, full Maven reactor, and core integration-test suite were not 
run.
   
   ---
   
   - [x] I hereby declare this contribution to be licensed under the [Apache 
License Version 2.0, January 2004](https://www.apache.org/licenses/LICENSE-2.0)
   - [ ] I hereby declare that I have filed an [Apache Individual Contributor 
License Agreement](https://www.apache.org/licenses/icla.pdf).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to