[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4899) 'Hibernate Configurations' view is not updated after hibernate console enabled project with configuration is deleted from workspace

[ https://jira.jboss.org/jira/browse/JBIDE-4899?page=com.atlassian.jira.plu... ] Vitali Yemialyanchyk commented on JBIDE-4899: --------------------------------------------- "A java launch configuration is removed since it refers to a specific java project and hence it gets deleted" - that makes sense IMO too. "The same thing could be said about Hibernate Launch Configurations - if they refer back to a project they also don't make sense to keep around. What is the counter argument for that ? Why should the launch config be kept around if the project it depends on is removed ? isn't that exactly the same as for the Java launch configs ?" "Hibernate Launch Configurations" - I do not understand. There is "Hibernate Console Configurations" and "Hibernate Code Generation Configurations". Only "Hibernate Console Configuration" refers to some project. "Hibernate Code Generation Configurations" refers too "Hibernate Console Configuration". So here we talk about "Hibernate Console Configuration". Next -> my arguments why we should not delete "Hibernate Console Configuration" with the reference project. Try to imagine simple situation - I have 2 projects with the same Hibernate settings. First project is the reference project. I delete it. I want use my Hibernate consol config with the second project. I just edit it, change "Project name". If I want delete my "Hibernate Console Configuration" I just select it, press delete button and confirm deletion - it is SOO SIMPLE. Why we should "generate surprise behavior" for users? -- 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