> -----Original Message-----
> From: Aaron Kamienski [mailto:[EMAIL PROTECTED]]
> I had asked about this previously on the list but got no reply.
> It seems (to me) to be a problem with the design, so if that's being
> reworked, there might be hope...
Ah sorry, I did not see your mail.
> I would like to be able to only do the report if Xalan is available.
> I currently can do this as long as I don't include a <report>
> sub-element like so:
[...]
I understand your problem.
Actually, this is because the build file resolution is done at startup, thus
if some instantiated classes related to attributes or elements import
classes that do not exist it will fail. Even if you do not call the task.
One solution is to do a lazy instantiation in all elements/attributes, but
it is not that simple in all cases. In your case, if you do not add the
<report> element it will work fine just due to this behavior.
--
Stephane Bailliez
Software Engineer, Paris - France
iMediation - http://www.imediation.com
Disclaimer: All the opinions expressed above are mine and not those from my
company.
