hsynkrtl commented on PR #211:
URL: 
https://github.com/apache/maven-toolchains-plugin/pull/211#issuecomment-6532661661

   I agree that a missing toolchain should generally be considered a 
configuration error. However, I believe the build author should decide whether 
it must be fatal.
   
   There are legitimate scenarios where toolchains are optional, for example 
across different development environments or CI pipelines.
   
   More broadly, I would like to see `skip` and `fail` (or not-to-fail) become 
standard configuration mechanisms across Maven plugins, ideally as part of 
Maven core:
   
   - `skip`: Control whether a goal is executed.
   - `fail`: Control whether a plugin failure aborts the build.
   
   The Maven Enforcer Plugin already offers a `<fail>` parameter, so this is an 
established concept within Maven.
   
   With `fail=true` as the default, existing behavior and backward 
compatibility are preserved. This adds flexibility without changing defaults.
   
   I don't think a feature should be dismissed simply because its use case is 
uncommon. Consistency and configurability across Maven plugins are valuable in 
their own right.


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