marking a plugin parameter as read-only is a choice of the plugin developer,
who does not consider configuration as a provided plugin/goal feature, but
wants to inject default values that are consistent with other POM configuration
if you think the plugin needs to be improved to be more flexible
elharo opened a new pull request #5:
URL: https://github.com/apache/maven-doxia-site/pull/5
@michael-o
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
U
Javier,
In upcoming Maven release 3.7
0 it won't be allowed to overwrite readonly attributes.
I am sorry, I don't know how to fix your issue.
Question for the community: can we drop the 'readonly' flag from the
'resources' field of checkstyle plugin?
I mean, it has always been writable up to no
Hi,
we are testing a config, that overwrites a readonly attribute, in Maven
Checkstyle plugin config, to be able to analyze a set of resource
folders in project root folder.
We don't want to define this spefic folders config in POM build
block, to avoid inherit that in child POMs, so we are
elharo opened a new pull request #4:
URL: https://github.com/apache/maven-doxia-site/pull/4
@michael-o
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
