> -----Original Message----- > From: Erik Hatcher [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 27, 2003 10:53 AM > To: Struts Developers List > Subject: Re: Investigating adding custom ant task to valid TLD > attributes bean mappings > > > First of all... why not use XDoclet to generate TLD files in > the first > place? They you are guaranteed to have valid accurate TLD files.
I don't think this would work as we need it to. Many of the standard attributes are implemented in base classes, rather than on the tag classes themselves. That in itself may not be a problem, but not all of the attributes should be exposed for every tag that extends the base class (since they're not all valid for all HTML tags, for example). Would it be possible to control something like that with XDoclet? -- Martin Cooper > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
