[
https://issues.apache.org/jira/browse/MNGSITE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15259470#comment-15259470
]
ASF GitHub Bot commented on MNGSITE-281:
----------------------------------------
GitHub user chonton opened a pull request:
https://github.com/apache/maven-site/pull/4
MNGSITE-281: update introduction to lifecycle with current practice r…
Using integration-test as the target from the command line doesn't do what
many users expect. The failsafe plugin does not report on results until the
verify phase. The cargo and tomcat plugins require at least the
post-integration-test phase to be run else the web containers are not stopped.
Jacoco does not collect coverage data until post-integration-test. For these
situations, it no longer is a useful practice to run integration-test as the
command line target. I recommend updating the introduction to remove
integration-test as one of the featured phases in the {A Build Lifecycle is
Made Up of Phases} section.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chonton/maven-site trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-site/pull/4.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4
----
commit 6b210d25bc1b45e963d60c85df2b54276b7ee6d6
Author: Chas Honton <c...@apache.org>
Date: 2016-04-27T03:10:06Z
MNGSITE-281: update introduction to lifecycle with current practice re:
integration-test
----
> Introduction to lifecycle update to reflect current practice wrt
> integration-test
> ---------------------------------------------------------------------------------
>
> Key: MNGSITE-281
> URL: https://issues.apache.org/jira/browse/MNGSITE-281
> Project: Maven Project Web Site
> Issue Type: Improvement
> Reporter: Charles Honton
> Priority: Minor
>
> Using integration-test as the target from the command line doesn't do what
> many users expect. The failsafe plugin does not report on results until the
> verify phase. The cargo and tomcat plugins require at least the
> post-integration-test phase to be run else the web containers are not
> stopped. Jacoco does not collect coverage data until post-integration-test.
> For these situations, it no longer is a useful practice to run
> integration-test as the command line target. I recommend updating the
> introduction to remove integration-test as one of the featured phases in the
> \{A Build Lifecycle is Made Up of Phases\} section.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
