On 7/18/2023 9:16 AM, Hervé Boutemy wrote:
Le lundi 17 juillet 2023, 22:49:16 CEST Slawomir Jaranowski a écrit :
Hi
Please try a never version of Maven and m-resources-p
Maven 3.3.9 is EOL - https://maven.apache.org/docs/history.html
m-resources-p has no parameter "resources"
m-resources-p
Le lundi 17 juillet 2023, 22:49:16 CEST Slawomir Jaranowski a écrit :
> Hi
>
> Please try a never version of Maven and m-resources-p
> Maven 3.3.9 is EOL - https://maven.apache.org/docs/history.html
>
> m-resources-p has no parameter "resources"
m-resources-p has a resources parameter
Hi
Please try a never version of Maven and m-resources-p
Maven 3.3.9 is EOL - https://maven.apache.org/docs/history.html
m-resources-p has no parameter "resources"
You should use resource configuration on project level not plugin
configuration, like in example:
Maven 3 not blocking setting read-only parameters is a known limitation
https://issues.apache.org/jira/browse/MNG-5001
in your case where you find a different behaviour between different Maven 3
releases, I imagine it's an additional side effect of this parameter not really
being expected to be
Hi Nikos,
That goal is only intended to be configured from project.build.resources.
You can rather use
https://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html
https://issues.apache.org/jira/browse/MRESOURCES-293
Delany
On Sun, 16 Jul 2023, 17:19 Nikos Dragazis, wrote:
Hi everyone,
I'd like to expose a deviation in maven's behavior regarding readonly
parameters in plugins. It seems that, starting from version 3.3.9, maven
no longer ignores configuration parameters for readonly arguments.
In more detail:
I have a project that follows the `war` packaging
