On 19/02/2008, at 9:50 PM, Stephen Connolly wrote:
My rule of thumb is to _always_ run the tests twice, once with
coverage and
once without. The test failure during the second (instrumented)
execution
should not fail the build.
Yes, this is the recommendation I always make too, to ensure
On Feb 18, 2008 8:03 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
> On 19/02/2008, at 3:15 AM, John Casey wrote:
> Things like:
> - running the tests twice by necessity
Having being burned by this little foible...
I often see people complain that the code coverage tools runs the unit tests
twice
On 19/02/2008, at 3:15 AM, John Casey wrote:
On Feb 17, 2008, at 3:48 PM, Brett Porter wrote:
- decent integration of code coverage plugins (we never got this
forked lifecycle quite right)
Can you shed some more light on this? Do we have specific test cases
that we can put into the build
On Feb 17, 2008, at 3:48 PM, Brett Porter wrote:
- decent integration of code coverage plugins (we never got this
forked lifecycle quite right)
Can you shed some more light on this? Do we have specific test cases
that we can put into the build?
I'll have to read over the rest of your pos
x, so let's take advantage of that
to see what we got wrong, and how we can correct it.
The page is here:
http://docs.codehaus.org/display/MAVEN/Atypical+Plugin+Use+Cases
Thanks in advance,
-john
---
John Casey
Committer and PMC Member, Apache Maven
mail: jdcasey at commonjava dot
That's not really the point. The point is that these behaviors
require exceptional logic to the main build process inside Maven.
They're a deviation of the normal once-per-project mojo, which is
geared to operate on the current project.
If you wanted to draw attention to something that does
On Wed, Feb 13, 2008 at 11:52 PM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
> John Casey wrote:
>
> > I'm trying to document some of the design problems with sort of exotic
> plugin
> > use cases, things like aggregation and use of ${reactorProjects}, that
> we're
> > running into under the current
John Casey wrote:
I'm trying to document some of the design problems with sort of exotic plugin
use cases, things like aggregation and use of ${reactorProjects}, that we're
running into under the current setup. I have proposals to address most of the
issues, but I'd love to hear what you would
nce with what works
and what doesn't from 2.0.x, so let's take advantage of that to see
what we got wrong, and how we can correct it.
The page is here: http://docs.codehaus.org/display/MAVEN/Atypical
+Plugin+Use+Cases
Thanks in advance,
-john
---
John Casey
Committer and P
