Heh, well it's been quite a while since I worked on it, so I can't say for
sure. I know that it at least worked for a few of my open source projects
(OSCore, PropertySet, etc), but I never did any testing beyond that.
-Pat
----- Original Message -----
From: "Andrew Stevens" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, June 27, 2003 10:13 AM
Subject: Pramati module
> Is it just me, or is the Pramati module broken at the moment?
>
> 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.
>
>
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
