[ http://issues.apache.org/jira/browse/GUMP-16?page=all ]
Leo Simons closed GUMP-16:
--------------------------
Resolution: Won't Fix
Fix Version: (was: Gump2)
The <regexp tag is really a poor man's way to define success/failure condition
for a project based on log output. Ideally, the ways to define success/failure
will become a lot more refined than this in gump 3 (for example act differently
based on different exit statuses, do more than just boolean success/failure)
and in the new version of the gump object model. There's currently 25
occurrences of <regexp in our metadata, which is feasible to fix "by hand" when
the time arises.
> Support for <regexp in <nag
> ---------------------------
>
> Key: GUMP-16
> URL: http://issues.apache.org/jira/browse/GUMP-16
> Project: Gump
> Type: Bug
> Components: Python-based Gump
> Versions: Gump2
> Environment: All
> Reporter: Adam Jack
>
> Gumpy needs to support <regexp
> http://jakarta.apache.org/gump/metadata/project.html#nag
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
