I was looking into issue XDT-84 ("when using the pramati subtask if you specify both jarname and destdir attributes, jarname must precede destdir or it will not populate the pramati deployment descriptors. not sure if this is a bug."), but it doesn't seem to want to run at all. All I get is errors about having to specify both destinationFile and templateFile config parameters. Looking at the subtask, I see that both those are set in the execute() method. However, unlike other modules which do this, it's not overriding the validateOptions method (which is why it's bombing out with these errors).
The strange thing is that, so far as I can tell from the CVS history, the Pramati subtask has always been this way (ever since it was added in March '02). And yet, the validateOptions method in TemplateSubTask predates this by several months. So has the Pramati module ever worked? Surely someone would have complained before now if it hasn't?
Andrew.
_________________________________________________________________
It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
