[ https://jira.jboss.org/jira/browse/JBIDE-4899?page=com.atlassian.jira.plu... ] Viacheslav Kabanovich reassigned JBIDE-4899: -------------------------------------------- Assignee: Vitali Yemialyanchyk (was: Viacheslav Kabanovich) I think description is put here by mistake instead of JBIDE-4902 -- 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-4899?page=com.atlassian.jira.plu... ] Denis Golovin updated JBIDE-4899: --------------------------------- Attachment: (was: hib-config-editor-error.png) -- 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-4899?page=com.atlassian.jira.plu... ] Vitali Yemialyanchyk commented on JBIDE-4899: --------------------------------------------- I do not understand what is wrong? I can't reproduce it or? STEP2 is not clear... I create java project, create hib. console config, delete java project, open hib. console config - it is correctly inform me about "The Java project zzz does not exist." -- 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-4899?page=com.atlassian.jira.plu... ] Denis Golovin reopened JBIDE-4899: ---------------------------------- -- 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-4899?page=com.atlassian.jira.plu... ] Denis Golovin commented on JBIDE-4899: -------------------------------------- Console configuration related to deleted project should also be deleted, Like java does for launch configurations. If Java project is deleted all launch configurations referenced to this project have the same fate to be deleted. -- 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-4899?page=com.atlassian.jira.plu... ] Vitali Yemialyanchyk resolved JBIDE-4899. ----------------------------------------- Resolution: Won't Fix Dima, JBIDE-4899.swf is about simple java project. Denis I understood what did you mean, thanks for the demo swf. I reproduce it, but I do not want to fix this issue, cause I did not see a problem here. More over I consider to delete Hibernate Console Config in such case is a wrong decision. I vote to close the issue with "Won't Fix" resolution. Here you have got the absolutly correct error message. I see no reason to discuss it more... Hibernate Console Config is not a java launch config - it just use the same convenient way for config save... -- 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-4899?page=com.atlassian.jira.plu... ] Dmitry Geraskov commented on JBIDE-4899: ---------------------------------------- This means that Hibernate Console Code Generation should be deleted too. (And all associated ConsoleConfiguration - not only the default one) -- 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-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

[ https://jira.jboss.org/jira/browse/JBIDE-4899?page=com.atlassian.jira.plu... ] Denis Golovin updated JBIDE-4899: --------------------------------- Fix Version/s: 3.1.0.CR1 (was: 3.1.0.M4) bulk move from M4 to CR1 -- 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-4899?page=com.atlassian.jira.plu... ] Dmitry Geraskov resolved JBIDE-4899. ------------------------------------ Resolution: Done Assignee: Anton Klimkovich (was: Dmitry Geraskov) Labels: new_and_noteworthy (was: ) -- 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-4899?page=com.atlassian.jira.plu... ] Dmitry Geraskov reopened JBIDE-4899: ------------------------------------ Assignee: Dmitry Geraskov (was: Anton Klimkovich) Reopened for discussion. Eclipse does not delte Project's launch configurations if button 'Delete Configurations when associated resource is deleted' is not selected. See Preferences->Run/Debug->Launching->Launch Configurations. I think we need to revert my changes and do the same thing, but I am not sure - seam project's console configuration still be deleted. -- 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-4899?page=com.atlassian.jira.plu... ] Dmitry Geraskov updated JBIDE-4899: ----------------------------------- Attachment: prefs.PNG Implmentet natural to Eclipse behaviour: see last checkbox. -- 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