[ 
http://issues.apache.org/jira/browse/TORQUE-73?page=comments#action_12456161 ] 
            
CG Monroe commented on TORQUE-73:
---------------------------------

Hmm, I think I found the problem here.  Velocity 1.3 has a runtime dependancy 
on having at least one of three logging mechanisms available, log4j, logkit, or 
avalon-logkit.  In the past, we supplied the logkit-1.01.jar as a dependency.  
But this has been dropped from the new version. (not sure why).

Adding log4j resolved the Velocity runtime dependancy but I'm not sure if this 
is the correct solution.

Anyone have good insight on which logging jar we should add back in?  I think 
Thomas V was using the new Avalon-Logkit?  Should we go to that as newer than 
the old original logkit?

> Missing log4j.jar for Torque Generator?
> ---------------------------------------
>
>                 Key: TORQUE-73
>                 URL: http://issues.apache.org/jira/browse/TORQUE-73
>             Project: Torque
>          Issue Type: Bug
>          Components: Generator
>    Affects Versions: 3.3
>         Environment: Windows XP
>            Reporter: Joerg Friedrich
>
> 1. I have downloaded the Torque 3.3 (RC1) Generator package.
> 2. I want to run the jdbc target; I set all properties as required in the 
> build.properties file
> 3. I set my ANT_HOME and JAVA_HOME (ANT 1.6.4 from Eclipse, JDK 1.5)
> 4. I execute ant -f build-torque.xml jdbc (actually, any other target has the 
> same problem)
> 5. I receive a velocity error
> 6. I install log4j.jar into the lib directory
> 7. It works!
> Maybe I am missing something, and it should work without log4j, but in my 
> environment it does not.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to