Multiple executions feature does not work

[aliaksei-dubrouski]

I have tried to use plugin as it described in Issue #9 , I have even tried to use exact plugin configuration with the same execution IDs, config file names, etc. But every time I run maven plugin fails with the same exception:

[ERROR] Failed to execute goal com.github.mcheely:requirejs-maven-plugin:1.1.0:optimize (default-cli) on project project: The parameters 'configFile' for goal com.github.mch
eely:requirejs-maven-plugin:1.1.0:optimize are missing or invalid -> [Help 1]

I am pretty sure both configs are okay, as plugin runs successfully, when I use standard configuration without multiple executions.
P.S. I am using plugin inside of a profile if it can affect anything.

[MattCheely]

The multiple execution support is built into maven itself, so I'd expect that if something wasn't working it would probably be a config issue. Can you attach your working single execution plugin config and the broken config for multiple executions from your pom.xml?

[aliaksei-dubrouski]

This configuration does NOT work:

                  <plugin>
                    <groupId>com.github.mcheely</groupId>
                    <artifactId>requirejs-maven-plugin</artifactId>
                    <version>1.1.0</version>
                    <executions>
                      <execution>
                        <id>Build the first thing</id>
                        <goals>
                          <goal>optimize</goal>
                        </goals>
                        <configuration>
                          <configFile>${basedir}/config1.js</configFile>
                        </configuration>
                      </execution>
                      <execution>
                        <id>Build the second thing</id>
                        <goals>
                          <goal>optimize</goal>
                        </goals>
                        <configuration>
                          <configFile>${basedir}/config2.js</configFile>
                        </configuration>
                      </execution>
                    </executions>
                    <configuration>
                        <optimizerFile>${basedir}/src/main/scripts/r.js</optimizerFile>
                        <filterConfig>true</filterConfig>
                    </configuration>
                  </plugin>

(removing optimizeFile parameter does not help).
I've installed plugin with a new name (fixed poms and props inside jar file). This configuration works flawless, except one thing that now I need third run and have to install plugin third time with a new name. Configuration files are absolutely the same for both cases:

                <plugin>
                    <groupId>com.github.mcheely</groupId>
                    <artifactId>requirejs-maven-plugin</artifactId>
                    <version>1.1.0</version>
                    <executions>

                        <execution>
                            <id>jsoptimize</id>
                            <phase>compile</phase>
                            <goals>
                                <goal>optimize</goal>
                            </goals>
                        </execution>
                    </executions>
                    <configuration>
                        <configFile>${basedir}/config1.js</configFile>
                    </configuration>
                </plugin>
                <plugin>
                    <groupId>com.github.mcheely</groupId>
                    <artifactId>requirejs-maven-plugin-2</artifactId>
                    <version>1.1.0</version>
                    <executions>
                        <execution>
                            <id>cssoptimize</id>
                            <phase>compile</phase>
                            <goals>
                                <goal>optimize</goal>
                            </goals>
                        </execution>
                    </executions>
                    <configuration>
                        <configFile>${basedir}/config2.js</configFile>
                    </configuration>
                </plugin>

[MattCheely]

Hm.... That's odd. Have you tried moving the "shared config" in your first example into the specific exec configurations, as shown below?

Also, does the plugin execution fail on the first or second run?

                     <plugin>
                        <groupId>com.github.mcheely</groupId>
                        <artifactId>requirejs-maven-plugin</artifactId>
                        <version>1.1.0</version>
                        <executions>
                          <execution>
                            <id>Build the first thing</id>
                            <goals>
                              <goal>optimize</goal>
                            </goals>
                            <configuration>
                              <configFile>${basedir}/config1.js</configFile>
                              <optimizerFile>${basedir}/src/main/scripts/r.js</optimizerFile>
                              <filterConfig>true</filterConfig>
                            </configuration>
                          </execution>
                          <execution>
                            <id>Build the second thing</id>
                            <goals>
                              <goal>optimize</goal>
                            </goals>
                            <configuration>
                              <configFile>${basedir}/config2.js</configFile>
                              <optimizerFile>${basedir}/src/main/scripts/r.js</optimizerFile>
                              <filterConfig>true</filterConfig>
                            </configuration>
                          </execution>
                        </executions>
                      </plugin>

[nithinkamath]

Am getting the same error,
[ERROR] Failed to execute goal com.github.mcheely:requirejs-maven-plugin:1.1.0:optimize (default-cli) on project project: The parameters 'configFile' for goal com.github.mcheely are missing or invalid.
Is there any workaround for this issue?

[nwhittaker]

+1

[akoskm]

@mcheely that's right, multiple executions are working fine, the issue is with @aliaksei-dubrouski's configuration / plugin invocation.
See http://stackoverflow.com/questions/649955/maven-error-with-multiple-executions-in-maven-deploy-plugin

[bringking]

Yes to build on what @mcheely and what @akoskm have stated, based on my research multiple executions should be bound to a lifecycle phase. For example-

     <execution>
                    <id>somepage</id>
                    <phase>generate-resources</phase>
                    <goals>
                        <goal>optimize</goal>
                    </goals>
                    <configuration>
                        <configFile>
                            ${widget.path.build}/optimize.js
                        </configFile>
                        <optimizerParameters>
                            <parameter>baseUrl=${widget.path}/somepage</parameter>
                            <parameter>out=${widget.path}/somepage/optimized.js</parameter>
                        </optimizerParameters>
                        <filterConfig>
                            true
                        </filterConfig>
                        <skip>
                            ${uglification}
                        </skip>
                    </configuration>
                </execution>

Then to optimize your resources you would run "mvn generate-resources". The reason for this, behavior is that when you call the goal directly, it doesn't try to process the executions, and it looks for the configuration at the plugin level. For instance-

<plugin>
  <groupId>com.github.bringking</groupId>
            <artifactId>requirejs-maven-plugin</artifactId>
            <version>2.0.2</version>
            <executions>
                <execution>
                    <id>activity</id>
                    <phase>generate-resources</phase>
                    <goals>
                        <goal>optimize</goal>
                    </goals>
                    <configuration>
                        <configFile>
                            ${widget.path.build}/optimize.js
                        </configFile>
                        <optimizerParameters>
                            <parameter>baseUrl=${widget.path}/somepage</parameter>
                            <parameter>out=${widget.path}/somepage/optimized.js</parameter>
                        </optimizerParameters>
                        <filterConfig>
                            true
                        </filterConfig>
                        <skip>
                            ${uglification}
                        </skip>
                    </configuration>
                </execution>
             </executions>
     <configuration>
                        <configFile>
                            ${widget.path.build}/optimize.js
                        </configFile>
                        <optimizerParameters>
                            <parameter>baseUrl=${widget.path}/someotherpage</parameter>
                            <parameter>out=${widget.path}/someotherpage/optimized.js</parameter>
                        </optimizerParameters>
                        <filterConfig>
                            true
                        </filterConfig>
                        <skip>
                            ${uglification}
                        </skip>
      </configuration>
</plugin>

A configuration like this will optimize "somepage" if you run "mvn generate-resources" and it will run "someotherpage" if you run "mvn requirejs:optimize"

Hope this helps.