eclipse 3.7: process-test-resources: Plugin execution not covered by lifecycle configuration

[GoogleCodeExporter]

The plugin works well with eclipse 3.6 but in eclipse 3.7 i get the error

Plugin execution not covered by lifecycle configuration: 
com.google.code.maven-replacer-plugin:maven-replacer-plugin:1.5.0:replace 
(execution: default, phase: process-test-resources)

eclipse does not find any matching m2e connector for it. 

                <plugin>
                        <groupId>com.google.code.maven-replacer-plugin</groupId>
                        <artifactId>maven-replacer-plugin</artifactId>
                        <version>1.5.0</version>

                        <executions>
                            <execution>
                                  <phase>process-test-resources</phase>
                                <goals>
                                    <goal>replace</goal>
                                </goals>
                            </execution>
                        </executions>
                        <configuration>

any suggestions how i can work around this problem?

Original issue reported on code.google.com by christia...@gmail.com on 24 May 2012 at 3:52

[GoogleCodeExporter]

Hmm, never seen this before. 1.5.0's artifactId is "replacer", not 
"maven-replacer-plugin". Perhaps changing this would help?

Original comment by baker.st...@gmail.com on 27 May 2012 at 4:43

• Changed state: Accepted

[GoogleCodeExporter]

I havnt heard anything on this for a while, so it's possibly no longer a 
problem. I will close it off and look into it further if the issue reoccurs.

Original comment by baker.st...@gmail.com on 17 Jun 2012 at 11:02

[GoogleCodeExporter]

Original comment by baker.st...@gmail.com on 17 Jun 2012 at 11:02

• Changed state: WontFix

[GoogleCodeExporter]

Still an issue. Even if I change artifactId to "replacer".

Original comment by eclipseguru@gmail.com on 21 Jun 2012 at 8:38

[GoogleCodeExporter]

still the issue exists...

Original comment by bigfishs...@gmail.com on 1 Oct 2012 at 10:18

[GoogleCodeExporter]

I have a fix for it this way below (having a lifecyle mapping for eclipse on 
what to do) you could use either 'ignore' or 'execute'...

...
    <pluginManagement>
        <plugins>
        <plugin>
                <groupId>org.eclipse.m2e</groupId>
                <artifactId>lifecycle-mapping</artifactId>
                <version>1.0.0</version>
                <configuration>
                    <lifecycleMappingMetadata>
                                    <pluginExecutions>
                                          <pluginExecution>
                                              <pluginExecutionFilter>
                                                <groupId>com.google.code.maven-replacer-plugin</groupId>
                                                <artifactId>replacer</artifactId>
                                                <versionRange>1.5.0</versionRange>
                                                <goals>
                                                  <goal>replace</goal>
                                                </goals>
                                              </pluginExecutionFilter>
                                              <action>
                                                  <execute></execute>
                                              </action>
                                              <comment>source: </comment>
                                         </pluginExecution>
                        </pluginExecutions>
                    </lifecycleMappingMetadata>
                </configuration>
            </plugin>

        </plugins>
    </pluginManagement>

  </build>
...

Original comment by bigfishs...@gmail.com on 1 Oct 2012 at 11:15

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Thanks bigfishstrm. I suppose this feature is not needing to be included in the 
replacer plugin anymore since you can dictate how it fires from myeclipse with 
the example you gave above.

Can you confirm this before I close this?

Original comment by baker.st...@gmail.com on 5 Oct 2012 at 11:35

[GoogleCodeExporter]

No response. Closing.

Original comment by baker.st...@gmail.com on 4 Nov 2012 at 5:38

• Changed state: WontFix

[GoogleCodeExporter]

Sorry to post to a closed issue, but has anyone achieved to hook the replacer 
plugin into the eclipse build? I'm aware of the lifecycle mapping m2e supports 
but even with the above snippet none of the defined replacements ever take 
place.

Any hints on this?

Original comment by jonas.zuberbuehler on 5 Feb 2013 at 11:12

[GoogleCodeExporter]

Same question as #10, Eclipse build doesn't seem to execute the defined 
replacements

Original comment by w.bervo...@aca-it.be on 10 Apr 2013 at 10:03

[GoogleCodeExporter]

Same thing here using maven 3.0.5, eclipse kepler.

The plugin does run but it doesn't replace anything: "Replacement run on 0 
file."

Original comment by ferre.ad...@gmail.com on 13 Nov 2013 at 11:52

[GoogleCodeExporter]

Note: i was using replacer 1.5.2.

I changed to 1.5.1 and it now works as expected

Original comment by ferre.ad...@gmail.com on 13 Nov 2013 at 12:10