gnodet commented on PR #13269:
URL: https://github.com/apache/maven/pull/13269#issuecomment-6147610985

   Thanks for the suggestion, @raupach-e2n! I'd actually prefer to keep the 
current phrasing for a couple of reasons:
   
   1. **Actionable path**: The message includes the actual path the user typed 
(e.g. `-f myproject/custom.xml`), not a hardcoded `pom.xml`. Without it the 
user has to guess which file was not found.
   2. **Context**: The `-f/--file` reference tells them exactly which argument 
to fix.
   3. **Consistency**: The `[ERROR] Error executing Maven.` header is standard 
Maven error framing used across the board — dropping it here would be 
inconsistent.
   
   The current output:
   ```
   [ERROR] Error executing Maven.
   [ERROR] POM file X specified with the -f/--file command line argument does 
not exist
   ```
   …is already a significant improvement over the previous double-printing. I 
think it strikes the right balance between brevity and actionability.


-- 
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