[
https://jira.jboss.org/jira/browse/JBIDE-4899?page=com.atlassian.jira.plu...
]
Vitali Yemialyanchyk commented on JBIDE-4899:
---------------------------------------------
"surprise behavior" - I mean if I as the user create and edit something X and
then if I delete something Y and then I get "surprise" -> X was deleted.
"Java launch configuration" - is a particular exceptional case... In my practice
sometimes I regret about such eclipse behavior - when I use some complex combination of
"Program arguments" & "VM arguments", in other cases I do not pay
attention for that.
Other argument to save as it is :) --->
there is no analog of "Hibernate Configurations View" for "Java launch
configuration" - this means "Java launch configuration" is more lightweight
thing then "Hibernate Configuration" ("Hibernate Launch
Configuration"). Moreover there are "Hibernate Code Generation
Configurations" which depends on "Hibernate Configuration".
'Hibernate Configurations' view is not updated after
hibernate console enabled project with configuration is deleted from workspace
-----------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-4899
URL:
https://jira.jboss.org/jira/browse/JBIDE-4899
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.0.M4
Reporter: Denis Golovin
Assignee: Dmitry Geraskov
Fix For: 3.1.0.M4
Attachments: JBIDE-4899.swf
1. EXECUTE: Create java project
2. EXECUTE: Enable Hibernate Console and add hibernate Console configuration
3. ASSERT: Configuration appears in Hibernate Configurations View
4. EXECUTE: Delete Java Project from step 1
5. ASSERT: Hibernate Configurations View doesn't contain configuration corresponded
to deleted project
--
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