Unknown phase in plugin execution causes build to stop ------------------------------------------------------
Key: MNG-3193 URL: http://jira.codehaus.org/browse/MNG-3193 Project: Maven 2 Issue Type: Bug Affects Versions: 2.1 Reporter: Stefan Seidel In Maven 2.0.7 one could disable the execution of a plugin in child projects by adding an id to the execution in the parent and then setting the execution phase for this id in the child pom to some non-existent (like "none"). This does not work anymore in Maven 2.1-xxx (I'm using the M2 Plugin for Eclipse). Although it is understandable to validate the given phase, this use case should prove that either the check should stay as forgiving as in previous maven versions or that at last an option to disable plugin executions in child POMs should be provided. Parent POM: {code} <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-jar-plugin</artifactId> <executions> <execution> <id>test-jar</id> <goals> <goal>test-jar</goal> </goals> </execution> </executions> </plugin> {code} Child POM: {code} <plugin> <artifactId>maven-jar-plugin</artifactId> <executions> <execution> <id>test-jar</id> <phase>none</phase> </execution> </executions> </plugin> {code} -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira