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 [3] Sylwester [ERROR] Failed to execute goal org.apache.maven.its.plugins:maven-it-plugin-artifact:2.1-SNAPSHOT:install (install) on project dependency: The parameters 'pomFile' for goal org.apache.maven.its.plugins:maven-it-plugin-artifact:2.1-SNAPSHOT:install are missing, read-only or invalid -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.its.plugins:maven-it-plugin-artifact:2.1-SNAPSHOT:install (install) on project dependency: The parameters 'pomFile' for goal org.apache.maven.its.plugins:maven-it-plugin-artifact:2.1-SNAPSHOT:install are missing, read-only or invalid [1] https://github.com/apache/maven/pull/240 [2] https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven/job/MNG-5001/ [3] https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven/job/MNG-5001/lastSuccessfulBuild/artifact/org/apache/maven/apache-maven/3.6.2-SNAPSHOT/ pt., 5 kwi 2019 o 09:06 Stephane Nicoll <stephane.nic...@gmail.com> napisał(a): > 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 <herve.bout...@free.fr> > wrote: > > > 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 grace period with warnings for people setting such read-only > > parameters > > before really breaking such abnormal builds > > > > Regards, > > > > Hervé > > > > Le jeudi 4 avril 2019, 13:22:17 CEST Stephane Nicoll a écrit : > > > 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; > > > > > > That property can be set when configuring the plugin and its value is > > > injected. > > > > > > What am I missing? > > > > > > Thanks, > > > S. > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
