[m2e-users] Plugin execution not covered by lifecycle configuration

["Damon Jacobsen" <dajacobsen@xxxxxxxxxxxxx>]

I have googled for an hour looking for a solution. I have a pom containing the plugin as following.

 

<plugin>

                        <groupId>org.apache.torque</groupId>

                        <artifactId>torque-maven-plugin</artifactId>

                        <version>3.3</version>

                        <executions>

                              <execution>

                                    <id>generate-sources-torque</id>

                                    <phase>generate-sources</phase>

                                    <goals>

                                          <goal>om</goal>

                                    </goals>

                              </execution>

                        </executions>

                        <configuration>

                              <targetDatabase>mssql</targetDatabase>

                              <generateBeans>true</generateBeans>

                              <objectIsCaching>false</objectIsCaching>

                              <enableJava5Features>true</enableJava5Features>

                              <addSaveMethod>false</addSaveMethod>

                              <subpackageBaseBean>beans</subpackageBaseBean>

                              <subpackageBean>beans</subpackageBean>

                              <complexObjectModel>false</complexObjectModel>

                              <useClasspath>false</useClasspath>

                        </configuration>

</plugin>

 

As per the page http://wiki.eclipse.org/M2E_plugin_execution_not_covered, is seems I need to somehow tell m2e to go ahead and "execute" the plugin. The quickfix only has the solutions of ignore, which I do not want, or discover, which there are no connectors for this. This worked fine in previous versions of m2e. How do I get the new version of m2e to behave as the previous one did with this plugin?

 

 

 

Damon Jacobsen

 

 

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
_____________________________________________________________________