----- Original Message -----
From: "Vincent Massol" <[EMAIL PROTECTED]>
To: "'Maven Developers List'" <[email protected]>
Sent: Monday, January 23, 2006 5:02 PM
Subject: [PROPOSAL] Integration testing proposal for Maven 2.0.x
Hi,
...
* We create a new surefire:test-integration MOJO bound to the
integration-test lifecycle
You meant "integration-test PHASE"?
And in what phase will integration tests be compiled? Now we compile them
(with our own plugin) in test-compile, but I think it is to early (if you
want only
invoke "mvn package", you don't need it compilation).
Another "problem" with it compilation is that all our testing artifacts
needed by
integration tests, and not by unit tests have scope "test". There is not
"it" scope.
So they all (there are really many artifacts needed by cactus) are included
in
classpath for unit tests. Are we going to do something to avoid this, or is
it ok?
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
