[
https://issues.apache.org/jira/browse/MRESOURCES-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17703117#comment-17703117
]
Tamas Cservenak commented on MRESOURCES-293:
--------------------------------------------
Peter is totally right here, *that is the correct way* to configure resources
(and sorry for doco being misleading Peter).
On the other hand, I feel that use of configurable (in plugin configuration
section) resource may become handy, as some sort of ad-hoc resource copying...
still, I consider Delany answer "plugin configuration. We never use
build/resources" as plain wrong.
In other words, resources should be configured as Peter wrote, but I can
understand there are (rare) cases where they are needed in some (probably
custom) invocation of m-resources-p, but that is NOT how we do it everyday.
Hence, I created PR and will make them read-write, but with a clause: this
decision MAY be altered anytime, even reverted as again, proper way is how
Peter wrote in comment above.
> Resources should not be read-only
> ---------------------------------
>
> Key: MRESOURCES-293
> URL: https://issues.apache.org/jira/browse/MRESOURCES-293
> Project: Maven Resources Plugin
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: Delany
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 3.3.1
>
>
> With Maven 3.9.0 I'm getting lots of these warnings
> {noformat}
> [WARNING] Parameter 'resources' is read-only, must not be used in
> configuration{noformat}
> Clearly it shouldn't be marked read-only
> https://maven.apache.org/plugins/maven-resources-plugin/examples/resource-directory.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
