But, more below...
Where should I put the Ant task class? Obviously, it would go in the "struts-el" tree, but I'm not sure of the logistics of this. The task can only be performed after the library is built, but I guess the task class has to be available when ant starts.
No, it doesn't. You just <taskdef> it after its compiled, not before.
I'd be glad to avoid writing an Ant task and just execute "java" in the build, but I can't figure out how I can make what happens in the execution of my class to cause the build to fail.
Just throw an exception from main and it should fail the build. If you are sure you are doing a fork="true" you could call System.exit(), but if you don't fork then you'll kill Ant without a warning.
Note that I'm only referring to the Struts-EL build, although it's conceivable we could also do this in the main build. It's still possible to mess up the "property name"->"setter" mapping, even if you just use the standard mapping. Catching the error at build time might save someone a few minutes.
Again, XDoclet to the rescue!
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
