|
From: Paul C. <can...@po...> - 2003-06-21 23:54:03
|
Xandy -- Sounds like a very good idea to me. I've logged it as a feature request: http://sourceforge.net/tracker/ index.php?func=detail&aid=758578&group_id=55296&atid=476506 The most obvious way to handle a forked JVM is through exit codes, though that's not necessarily the best. We might consider setting different properties for the different severity levels: something like macker.error, macker.warning, macker.info, and then macker.exception or macker.failure for rules syntax, etc. The property names should respect Ant conventions and precedent from the JUnit task, and should be easy to use in Ant-style conditionals. If anybody implements this, I'll welcome the patch. Paul On Saturday, June 21, 2003, at 03:43 PM, Xandy Johnson wrote: > I'd like to see the Macker Ant Task have the ability to set Ant > properties both on error conditions and on rule violations. This would > be very much like the failureProperty and errorProperty of the JUnit > Ant > Task. The errorProperty would be set if there is some error condition > other than rule violations (e.g. a malformed rule) and the > ruleViolationProperty would be set if there are rule violations. A Use > Case for such a feature is sending email only if there are problems. > > I spent a few minutes starting this, but that was over a week ago. > I've > attached the trivial patch of what I had so far. I'm not even sure of > its state. The main thing I don't know how to do is to handle the case > of a forked JVM. I wish I had the time to see this through, but I'm > falling further and further behind on my "real" tasks at work and I'm > not sure when I'd get to this. I'd really appreciate if someone else > would take the idea and run with it. > > Thanks, > Xandy > <ruleViolationProperty.patch><mime-attachment> |
