You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Charles Honton (JIRA)" <ji...@apache.org> on 2016/04/27 05:19:12 UTC
[jira] [Created] (MNGSITE-281) Introduction to lifecycle update to
reflect current practice wrt integration-test
Charles Honton created MNGSITE-281:
--------------------------------------
Summary: 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)