Maven – m2e lifecycle-mapping not found

Specify the fully-qualified goal in the form of:

mvn groupID:artifactID:version:goal

For example:

mvn sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi

EDIT: I'm modifying my answer to cover the update of the initial question and a comment from the OP.

I won't cover all the details but, it the particular case of the antrun plugin, you could just run:

mvn antrun:run

But now that you've updated the question, I understand that things are a bit more complicated than what I thought initially and I don't think that this will actually work. I mean, invoking mvn antrun:run won't fail but it won't pick up the configuration of the execution bound to the test phase.

The only (ugly) solution I can think of would be to add another maven-antrun-plugin configuration in a specific profile, something like this:

  <plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-antrun-plugin</artifactId>
    <version>1.3</version>
    <dependencies>
      <dependency>
        <groupId>com.googlecode.jslint4java</groupId>
        <artifactId>jslint4java-ant</artifactId>
        <version>1.3.3</version>
      </dependency>
    </dependencies>
    <configuration>
      <tasks>
        <ant antfile="${basedir}/jslint.xml">
          <property name="root" location="${basedir}" />
          <target name="jslint" />
        </ant>
      </tasks>
    </configuration>
  </plugin>

And to use this profile when calling antrun:run:

mvn antrun:run -Pmyprofile-for-antrun

In my case of a similar problem, instead of using Andrew's suggestion for the fix, it worked simply after I introduced <pluginManagement> tag to the pom.xml in question. Looks like that error is due to a missing <pluginManagement> tag. So, in order to avoid the exceptions in Eclipse, one needs to simply enclose all the plugin tags inside a <pluginManagement> tag, like so:

<build>
    <pluginManagement>
        <plugins>
            <plugin> ... </plugin>
            <plugin> ... </plugin>
                  ....
        </plugins>
    </pluginManagement>
</build>

Once this structure is in place, the error goes away.