[ https://jira.jboss.org/jira/browse/JBIDE-2608?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-2608: -------------------------------------------- where did you get that statement from ? hibernate.cfg.xml is not automatically looked up in the classpath so can't see how that can be true. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2608?page=com.atlassian.jira.plu... ] Max Rydahl Andersen resolved JBIDE-2608. ---------------------------------------- Resolution: Rejected Was surprised to see that this was actually committed to trunk without being marked as fixed. In any case, i'm rolling this back when JBIDE-719 is being fixed since I can see it is not implemented correctly. The statement/warning is correct a runtime if there is both a /hibernate.properties and /hibernate.cfg.xml, but this is *not* related to the properties files that are possible to setup in console configuration. Here the propertiies are available to *explicitly* override what is specified in persistence.xml/cfg.xml AND any overridable properties found in /hibernate.properties in the classpath. Thus this warning is saying the complete opposite of what is actually going on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2608?page=com.atlassian.jira.plu... ] Vitali Yemialyanchyk reassigned JBIDE-2608: ------------------------------------------- Assignee: Vitali Yemialyanchyk (was: Anton Klimkovich) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2608?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-2608: -------------------------------------------- you want to explain every fields semantics with a warning ? Until now the rules are simple - priority goes from top to bottom. This issue made me fix JBIDE-719 to actually have the connection before the properties file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-2608?page=com.atlassian.jira.plu... ] Max Rydahl Andersen resolved JBIDE-2608. ---------------------------------------- Resolution: Out of Date -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira