> We use a custom classloader with Jetty 5.0. Probably because
> of Jetty's dependence on commons logging, Jetty was confused
> over Jira's inclusion of the same jar. Also, since Jira uses
> log4j to implement the logging, there was some classloading
> confusion over where to find it.
>
> To get Jira running, I removed the commons-logging jar from
> Jira and placed log4j in jetty/ext/ (where commons-logging
> already was). Also, I symlinked the Postgres JDBC jar into
> Jira's WEB-INF/lib directory.
> –