current userdetails.war release still uses hard-coded paths to tomcat logs

[mbohun]

current userdetails.war release still uses hard-coded paths to tomcat logs (the tomcat dir name is hard-coded), for example: /var/log/tomcat6/userdetails.log (might move/link to userdetails issue tracker)

ubuntu@mbohun-bubuntu12:/tmp$ find /var/log/tomcat7 | xargs grep userdetails
/var/log/tomcat7/catalina.out:INFO: Deploying web application archive /var/lib/tomcat7/webapps/userdetails.war
/var/log/tomcat7/catalina.out:INFO: validateJarFile(/var/lib/tomcat7/webapps/userdetails/WEB-INF/lib/servlet-api-2.3.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
/var/log/tomcat7/catalina.out:[userdetails] No external configuration file defined.
/var/log/tomcat7/catalina.out:[userdetails] (*) grails.config.locations = []
/var/log/tomcat7/catalina.out:java.io.FileNotFoundException: /var/log/tomcat6/userdetails.log (No such file or directory)
/var/log/tomcat7/catalina.out:java.io.FileNotFoundException: /var/log/tomcat6/userdetails-stacktrace.log (No such file or directory)
/var/log/tomcat7/catalina.out:[userdetails] No external configuration file defined.
/var/log/tomcat7/catalina.out:[userdetails] (*) grails.config.locations = []
/var/log/tomcat7/catalina.out:SEVERE: Context [/userdetails] startup failed due to previous errors
/var/log/tomcat7/catalina.out:SEVERE: The web application [/userdetails] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

[m-r-c]

This has been fixed in version 0.2 of User Details