Laurie Harper wrote:
Laurie Harper wrote:
Ted Husted wrote:
On 9/14/05, Laurie Harper <[EMAIL PROTECTED]> wrote:
James Mitchell setup some automatic tests for the taglib, though a lot
of the behavior is still tested through the tag-exercises application.
Niall is correct. When I've applied taglib patches, the bullwork is
always setting up tests that first prove that there's a problem, and
then prove that the patch fixes it.
Ah, yes, I see the test-cactus stuff in svn. I'll see if I can get
that going before I start making any changes.
Well, I got them going... Are these tests maintained/used? The reason I
ask is that there are over 1100 failures! All but 29 of them look to be
the same thing, though, which I'm hoping will be a configuration issue I
can get rid of simply.
Given the number of tests that exist, it would seem well worth getting
them included in the nightly builds if they're not already (the maven
build in svn has the cactus report commented out, so I'm guessing
they're not being run at the moment). I'll try to post the necessary
diffs to allow that later tonight (he said with hopeless optimism ;-)
Don't mind me. I'm now down to only 30 errors, mostly complaints about
'locale' not being a valid attribute for the <html:html/> tag. I'll look
at cleaning the remaining failures up over the weekend.
The reason I got so many failures initially is because the maven build
(specifically the xdoclet plugin) is failing to generate the
struts-config.xml file. The appropriate goals / Ant tasks in the xdoclet
plugin are being called OK, it's just not doing anything.
I gave up trying to figure out why; if anyone here has any ideas let me
know, otherwise I'll follow-up on the xdoclet lists. For the time being
I just created a struts-config.xml by hand.
Bedtime!
L.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
