[EMAIL PROTECTED] wrote:
Ah, I was fooled by the package name indeed. Thanks for
spotting that Jan. I'm not sure there's a process for that,
but shouldn't the batik folks be warned not to use (usurp)
Ant's package names? --DD
Changing the package name is difficult for BWC reasons, but a hint
>Ah, I was fooled by the package name indeed. Thanks for
>spotting that Jan. I'm not sure there's a process for that,
>but shouldn't the batik folks be warned not to use (usurp)
>Ant's package names? --DD
Changing the package name is difficult for BWC reasons, but a hint would
be helpful.
I won
] [mailto:[EMAIL PROTECTED]
>Envoyé : 14 mars 2006 03:48
>À : user@ant.apache.org
>Objet : AW: taskdef, class not found
>
>The classname you provided sounds like one of Ant's, because
>Ant uses org.apache.tools.ant as main package. But the default
>file for taskdefs [1]
The classname you provided sounds like one of Ant's, because Ant uses
org.apache.tools.ant as
main package. But the default file for taskdefs [1] does not list that
class. And there is no such
class in the repo [2].
So this class is to be declared as other external tasks: taskdef or
xmlns (with all