[hibernate-issues] [Hibernate-JIRA] Commented: (HBX-1015) Classes from project's classpath block configuration view

Dmitry Chuyko (JIRA) noreply at atlassian.com
Mon Nov 19 10:48:59 EST 2007


    [ http://opensource.atlassian.com/projects/hibernate/browse/HBX-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_28888 ] 

Dmitry Chuyko commented on HBX-1015:
------------------------------------

For our particular needs it works. I've replaced log4j-1.2.11.jar with log4j-1.2.15.jar (renamed). So could you please at least update log4j to the latest version asap (CR2 maybe, as I see CR1 still use 1.2.11)?

> Classes from project's classpath block configuration view
> ---------------------------------------------------------
>
>                 Key: HBX-1015
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1015
>             Project: Hibernate Tools
>          Issue Type: Bug
>          Components: eclipse
>    Affects Versions: 3.2.beta11
>            Reporter: Dmitry Chuyko
>            Priority: Blocker
>
> Let eclipse project refer to jcl104-over-slf4j library ver. 1.4.2 or log4j incompatible with one used in tools plugin. Then user is unable to open project's configuration in hibernate configurations view. The plugin creates classloader that uses project's classpath and the classloader is used to analyse classes in a configuration. But classes loaded by this classloader (log4j) start being used by tools plugin itself and that leads to errors like NoSuchMethodError when versions are incompatible. Dialog with stack trace is shown and configuration details are not displayed.

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

        



More information about the hibernate-issues mailing list