[
http://jira.codehaus.org/browse/MNG-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98047
]
Nelz commented on MNG-2010:
---------------------------
To Jason:
If we take the "simple" example of a self-contained web application with just a
single WAR artifact, I think that requiring a multi-module build is kind of
overkill. (In an enterprise scenario, I can see separating out the tests,
especially if there is a client generated from the single WAR artifact, as is
the case with Web Services...)
Hypothetically, let's look at a multi-module with the first module building the
WAR file, and a second module to test the WAR file. What stops a developer
from going down to the first module and just building/deploying that artifact?
Now, the artifact is uploaded to whatever internal repository without being
tested.
One of the things I really cherish about the Maven lifecycle is how it enforces
that tests must pass *before* the artifact makes out of the local box...
To John:
I do think these phases are important, for all the same reasons they are
important before the (unit) tests. And, much like what I said above, I think
it is *very* important to test before it gets out of the current developer's
workspace. You are right, we probably won't have many people typing "mvn
process-integration-test-resources" (other than the build developers who want
to test up to that point...), but we sure will have people typing "mvn
install". And in my opinion, having the integration tests do their thing
before that 'install' point is *muy importante*...
Also, there *is* already provision for doing post-processing for cleanup, it's
the "post-integration-test"... And if you are talking about using the (unit)
test functionality for doing the post-processing stuff in a multi-module build,
that is why I added the "post-test" phase in my submitted patch...
To No One In Particular:
I believe the two parallel cycles of 'test' and 'integration-test' are
important for robust artifacts. The (unit) tests serve to test as a white-box,
co-locate type of environment, and the integration tests serve to test the
artifact like a black-box, separate client.
> Add new lifecycle phases for IT
> -------------------------------
>
> Key: MNG-2010
> URL: http://jira.codehaus.org/browse/MNG-2010
> Project: Maven 2
> Issue Type: Task
> Components: integration tests, Plugins and Lifecycle
> Reporter: Vincent Massol
> Fix For: 2.0.x
>
> Attachments: MNG-2010-maven-lifecycle.patch, MNG-2010-site.patch
>
>
> Namely:
> * generate-integration-test-sources
> * process-integration-test-sources
> * generate-integration-test-resources
> * process-integration-test-resources
> * integration-test-compile
> and possibly a:
> * integration-test-package
--
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
