Hi,
I think I found a place where you can add the verification of read-only
Mojo parameters, see [1]
For few tests looks it works correctly, we have one ITs failing [2].
Could you help with more testing? The code can be found in MNG-5001 branch
and compiled version - ready for download from our CI
Thank you very much for confirming Hervé. It would be nice if we had a way
to identify that the value was set and then take an appropriate action in a
custom plugin forthe time being.
Has anybody done that to workaround the issue maybe?
On Fri, Apr 5, 2019 at 8:21 AM Hervé BOUTEMY wrote:
> sadl
sadly nothing: this is a known limitation in Maven 3 (that did not exist in
Maven 2)
https://issues.apache.org/jira/browse/MNG-5001
I never had time to dig precisely into source code to see how hard the fix
would be. What I know is that when the fix will be available, we'll probably
need a grac
Hey,
I have a weird case trying to deprecate a "finalName" property where said
property can still be set by the user.
Here is the definition:
/**
* Name of the generated archive.
* @since 1.0
*/
@Parameter(defaultValue = "${project.build.finalName}", readonly = true)
private String finalName;
