Repository navigation
[MNG-3069] Parameters not passed to second execution of the same plugin. #4833
Description
Scott Morrison opened MNG-3069 and commented
If a plugin is loaded twice consecutively, parameters are not passed the second time.
For a (really) minimal case,
svn co http://katlas.math.toronto.edu/svn/arxivwiki/trunk/bug/
and "mvn package".
With mvn -version
Maven version: 2.0.7
Java version: 1.6.0_01
OS name: "windows xp" version: "5.1" arch: "x86"
I see
[INFO] [configuration-bug:plugin-configuration-bug {execution: plugin-configurat
ion-bug 1}]
String parameter: execution #1
File parameter: C:\scott\projects\svn-checkouts\arxivwiki\trunk\bug\demo\file1.t
xt
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] One or more required plugin parameters are invalid/missing for 'configura
tion-bug:plugin-configuration-bug'
[0] inside the definition for plugin: 'plugin-configuration-bug-plugin'specify t
he following:
<configuration>
...
<sp>VALUE</sp>
</configuration>.
Curiously, when running "mvn install" within eclipse, with exactly the same project, everything works just fine!
Affects: 2.0.7
Activity
jira-importer commentedon Jun 24, 2007
Scott Morrison commented
Oops, I meant run "mvn install" after checking out from svn, not "mvn package". Sorry.
jira-importer commentedon Jun 24, 2007
Scott Morrison commented
I realise this can be fixed by smushing the two uses of the plugin into one, with two <execution/> items, but this means I can't run some other plugin in between. :-(
jira-importer commentedon Oct 29, 2007
Brett Porter commented
you can't declare a plugin twice in the POM - and the order in the POM is not the order they are executed. This is defined by the lifecycle. You can order the executions to ensure the same ordering within a given phase of the lifecycle.