There are these in App.java
/** return code for ok processing */
private static final int RC_OK = 0;
/** return code from command prompt when a bad argument is passed */
private static final int RC_BAD_ARG = 10;
/** return code from command prompt when initialization fails */
private static final int RC_INIT_ERROR = 20;
/** return code from command prompt when a goal isn't found */
private static final int RC_NO_GOAL = 30;
/** return code for bad repository configuration */
private static final int RC_BAD_REPO = 40;
/** return code for a goal with no actions */
private static final int RC_EMPTY_GOAL = 50;
/** return code for a goal that failed */
private static final int RC_GOAL_FAILED = 60;
/** return code for a goal failed from jelly exception being thrown */
private static final int RC_JELLY_FAILED = 70;
/** return code for a failure due to Jelly issues */
private static final int RC_BAD_JELLY = 80;
/** return code for a failure due to anything else */
private static final int RC_OTHER_FAILURE = 90;
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Henri Yandell <[EMAIL PROTECTED]> wrote on 14/08/2003 09:47:19 AM:
>
> I've not been using Anthill, but am doing continuous integration with
> nightly build scripts [assuming that nightly counts as continuous].
>
> I've considered an error to be the failure to produce an output. So if
no
> *ar is created as a part of the build, the build failed, and if a docs/
> was not made as a part of 'maven site', then the site build failed.
>
> It would be nice if Maven would set up some nice error codes for
different
> failure reasons.
>
> 1 = DEPENDENCIES FAIL [if it exits here]
> 2 = SRC WON'T COMPILE
> 3 = TEST SRC WON'T COMPILE
> 4 = TESTS FAIL
>
> etc etc.
>
> The cludgy success-test might not work for you, but has managed to hang
> together enough for my needs.
>
> Hen
>
> On Wed, 13 Aug 2003, Nelson, Scott (MAN - Corporate) wrote:
>
> > Hey everybody,
> > I am new to maven and I am in the process of setting up a continuous
> > integration environment with anthill using maven. The problem I am
having
> > is maven doesn't seem to return anything other than a 0 for a return
code
> > therefore I always get a build success regardless of the output from
the
> > executed the maven goals.
> > I was wondering does maven supply different return codes for a build
success
> > and build failure?
> > Do I just have to set the property like maven.test.failure.ignore to
false?
> >
> > If this property is set, will maven return a 1 when a build failure is
> > thrown or some other non-zero value? Anthill is looking for a 1 to
signify
> > that the build failed.
> > Any help in understanding this would be greatly appreciated.
> > Thanks,
> > Scott
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
