I have no issue with maven site succeeding if tests fail.
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
Eric Dobbs
<[EMAIL PROTECTED] To: Turbine Maven Users List
<[EMAIL PROTECTED]>
et> cc:
Subject: separate unit test failures from
doc generation (was Re:
06/13/02 09:24 Calling <fail/> if <junit/> fails)
AM
Please respond
to "Turbine
Maven Users
List"
Hi All.
Sounds to me like the specific use case that's being
requested is this:
Let the docs be generated even (especially?) when the
unit tests are failing.
I agree with Jeff that the .jar should not be created
if the unit tests are failing. Let Maven enforce the
good programming habits.
I have no objections to allowing the docs generation
proceed if unit tests are failing. Perhaps including
email nags if the unit tests are failing.
So the website feedback is present, and the .jar isn't
built unless tests pass.
What do you think?
-Eric
On Wednesday, June 12, 2002, at 04:32 PM, John Keyes wrote:
> The reason why I asked is that for our nightly builds
> it would be nice to have the site created even if
> the unit tests fail. A mail is sent to indicate build
> success or failure. It would then be the responsibility
> of each developer working on the project to check the
> reports to see why the build failed.
On Wednesday, June 12, 2002, at 03:35 PM, Martin van den Bemt wrote:
> And don't worry failing will be the default ;) (that is what I want when
> developing, but my automated builds don't like failing too much, since
> the site will never get an update that way, which was the reason in the
> first place to make that simple hack...)
[snip]
> The problem with this best practice is, is that it kills all the
> feedback you can get via a nice site that something is wrong and what is
> wrong. (which is, at least for me, one of the reasons why I use maven in
> the first place). I want my development site to reflect the latest
> nigthly build and not the latest without failing tests.
[snip]
> Getting a nag mail from gump is also nice, but is highly outclassed by
> the feedback maven can give us if it can actually finish a build where
> tests are failing.
--
To unsubscribe, e-mail: <
mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <
mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
