maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MNGSITE-281) Introduction to lifecycle update to reflect current practice wrt integration-test
Date Sun, 01 May 2016 10:19:13 GMT

     [ https://issues.apache.org/jira/browse/MNGSITE-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Heinz Marbaise closed MNGSITE-281.
---------------------------------------
    Resolution: Fixed

Has been done by Mirko via [r1741510|http://svn.apache.org/r1741510]

> 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
>            Assignee: Mirko Friedenhagen
>            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)

Mime
View raw message