Hi Hilco,

Actually, the ant build is the standard build. The maven build is still experimental. (Though I thought it ran those tests).

Basically, most of the tests are run via junit in one big TestSuite. But there's 3 or 4 that depend on ant (or depend on custom classpath settings). Those are in testcases.xml. If you do:

"ant test"

they all are called.

WILL

----- Original Message ----- From: "Hilco Wijbenga" <[EMAIL PROTECTED]>
To: "Velocity Developers List" <[email protected]>
Sent: Friday, November 18, 2005 10:04 AM
Subject: Re: [PATCH] TexenTask - Support for <property> and <propertyset>


ant? I assume you mean maven? Or am I in the wrong source tree?

Here's what I did:

I created
test/texen/templates/nested_elements.vm
test/texen/compare/nested_elements.txt

I updated
test/texen/templates/Control.vm
test/texen-classpath/jar-contents/Control.vm
src/test/org/apache/velocity/test/TexenTestCase.java
build/testcases.xml

The 'nested_elements.*' are my template and the expected result after
merging. The 'Control.vm's contain

#set ( $sourceFile = "nested_elements.txt" )
$generator.parse("nested_elements.vm",$sourceFile)

(a simple copy&paste from the book.* entry).

In TexenTestCase.java I've added another 'isMatch' line

!isMatch(
 RESULTS_DIR, COMPARE_DIR,
 "nested_elements",
 "txt","txt"
)

Running maven clean jar (or maven test) clearly runs TexenTestCase (it
fails) and I can see that my code is being used. But as far as I can
tell build/testcases.xml is totally ignored. I first added an <echo> tag
to the test-texen target but didn't see it show up. I've even added a
<xyz/> tag expecting a spectacular failure but I don't see anything
strange happening. :-(

Clearly, I've missed something. :-)

Thanks,
Hilco

On Fri, 2005-11-18 at 06:02 -0800, Will Glass-Husain wrote:
Silly question but did you run "ant test"?



---------------------------------------------------------------------
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]

Reply via email to