well, i finally found the culprit.
the commons-logging.jar from the xdoclet cvs and the commons-logging.jar
that i downloaded from jakarta.apache.org don't seem to be exactly the
same. not sure why, but ant/xdoclet complained when i tried using the one
from jakarta.apache.org.
also, i believe that the absolute references to the .jars (from before)
were not helping. after consolidating all the required .jars under my ant
project's lib dir and removing everything from the CLASSPATH env var, i was
able to discover the incompatibility between xdoclet commons-logging.jar
and apache commons-logging.jar.
thank you very much for your help david. your kindness is much appreciated.
now back to programming... :)
At 14:11 02/07/01 -0400, you wrote:
>That seems strange. The only reason I could think of is that somehow the
>path you specified to commons-logging.jar in your build file was wrong.
>
>IMHO, you really shouldn't have *anything* in your CLASSPATH env var.
>Putting stuff in your env is always dangerous, whether it be PATH,
>LD_LIBRARY_PATH, CLASSPATH, etc. - since it builds up assumptions when you
>write/run stuff that picks it up.
>
>Can you verify that the commons-logging.jar is *really* where ant thinks
>it was? Test it by using the echo task in ant to print out your
>${apache.commons.logging.jar} variable (from the build.xml you sent me).
><echo message="${apache.commons.logging.jar}"/>
>Then ls -l a copy/paste in a console window of that echo to make sure
>it's really there.
>
>David
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
