[
https://jira.jboss.org/jira/browse/JBIDE-4899?page=com.atlassian.jira.plu...
]
Max Rydahl Andersen reopened JBIDE-4899:
----------------------------------------
Assignee: Dmitry Geraskov (was: Denis Golovin)
One could argue both ways.
A java launch configuration is removed since it refers to a specific java project and
hence it gets deleted - that makes sense IMO.
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 ?
note, if the launch config doesn't point to the project and the project just point to
the launch config the launch config should not be deleted.
'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