cowwoc commented on PR #389: URL: https://github.com/apache/maven-build-cache-extension/pull/389#issuecomment-3374280403
> To achieve this, I suggest the following: > > For each plugin, export its all parameters to xml (per plugin). > For the exported parameters, annotate each one as either "behavioral" or "functional." (further categorization might also help). For example, the number of compiler threads or log level would be considered behavioral parameters, whereas the target level would be functional. > The goal is to create a closed and matching set of parameters for default configurations for every plugin, every goal. The current implementation does not enforce the categorization of all parameters, which can lead to incorrect behavior if the plugin is modified (for instance, if a critical parameter is renamed). > > Ideally, the default configuration should fail on encountering an unknown parameter or at least emit a warning. @AlexanderAshitkin So if I understand you correctly, for the limited number of plugins that we supply defaults for, you want to provide enhanced validation to ensure that we log a warning if a user attempts to track changes of a non-existent or behavioral parameter. Is that correct? -- 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]
