[
https://issues.apache.org/jira/browse/SUREFIRE-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16902463#comment-16902463
]
Hüseyin Kartal commented on SUREFIRE-1686:
------------------------------------------
Obviously the documentation of the failsafe plugin means something different
than the documentation of the surefire (and quite all other plugins). Anyway.
Why just not behave as other plugins (surefire) and keep the pom clear by
respecting the paradigm of *Convention over Configuration.*
> Failsafe doesn't bind to lifecycle as documented
> ------------------------------------------------
>
> Key: SUREFIRE-1686
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1686
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Failsafe Plugin
> Affects Versions: 2.22.2
> Reporter: Hüseyin Kartal
> Assignee: Robert Scholte
> Priority: Major
>
> When configured a pom as follow:
> {noformat}
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-failsafe-plugin</artifactId>
> </plugin>
> </plugins>{noformat}
> the resulting effective-pom is:
> {noformat}
> <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>2.22.2</version>
> <executions>
> <execution>
> <id>default-test</id>
> <phase>test</phase>
> <goals>
> <goal>test</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> <plugin>
> <artifactId>maven-failsafe-plugin</artifactId>
> <version>2.22.2</version>
> </plugin>
> {noformat}
> The failsafe plugin doesn't bind its goals to the lifecycles as documented.
> * Binds by default to the [lifecycle
> phase|http://maven.apache.org/ref/current/maven-core/lifecycles.html]:
> {{integration-test}}.
> * Binds by default to the [lifecycle
> phase|http://maven.apache.org/ref/current/maven-core/lifecycles.html]:
> {{verify}}.
> To respect the convention over configuration aspect of maven, these default
> bindings should be fixed. And should not needed to defined as done in the
> examples in the documentation.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
