tillkuhn opened a new issue, #1680: URL: https://github.com/apache/maven-mvnd/issues/1680
### Affected version 1.0.6 ### Bug description ## Summary When using `mvnd -fae` (intended as shorthand for `--fail-at-end`), the flag is incorrectly parsed as separate flags (`-f`, `-a`, `-e`), causing plugin goals to receive corrupted or incorrect working directory/base path values. This does not occur with Maven's `mvn -fae` or when using `mvnd --fail-at-end`. ## Expected Behavior `mvnd -fae` should be equivalent to `mvnd --fail-at-end`, and plugins should execute with the correct base paths regardless of which form is used. ## Actual Behavior When running `mvnd -fae`, plugins receive incorrect directory paths. For example, the `xml-maven-plugin:transform` goal fails with: ``` [ERROR] The directory /path/to/project/ae/docs, which is a base directory of a ValidationSet or TransformationSet, does not exist. ``` The spurious `ae/` directory component appears to come from the misinterpreted `-a` and `-e` flags. ## Steps to Reproduce 1. Use any Maven project with a plugin that operates on file paths (e.g., `xml-maven-plugin`) 2. Run: `mvnd -fae clean install` 3. Observe path corruption in plugin execution ## Workaround Use the long form flag instead: ```bash mvnd --fail-at-end clean install ``` ## Environment - mvnd: 1.0.6 darwin-aarch64 - Maven: 3.9.16 - Java: 25.0.3 (Temurin) - OS: macOS 26.5.1, aarch64 (but also experienced on Linux CI runners) ## Additional Context - `mvn -fae` works correctly with standard Maven - `mvnd --fail-at-end` works correctly - This suggests a flag-parsing regression specific to mvnd's handling of compound short flags The issue is not immediately obvious to users switching from Maven to mvnd, making it a usability/documentation concern at minimum. -- 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]
