I've got a locally changed version of App that uses negative return codes
and has a set of them to match different failure conditions:
/** 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;
Votes?
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
"James CE Johnson" <[EMAIL PROTECTED]> wrote on 18/09/2002 10:47:46 PM:
> > I would like to suggest that Maven returns a non-zero return code when
> > a build fails. We use Gump for continuous builds and this uses the
> > return code to post success or failure messages in its build summary.
> >
> > Dave
>
> I think this would be pretty easy by adding a System.exit(100) in
> maven.app.App.doMain() on anything other than a successful compile.
>
>
>
> --
> To unsubscribe, e-mail: <mailto:turbine-maven-user-
> [EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:turbine-maven-user-
> [EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
