[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3664) Problems with ConsoleConfiguration creation
[
https://jira.jboss.org/jira/browse/JBIDE-3664?page=com.atlassian.jira.plu...
]
Dmitry Geraskov commented on JBIDE-3664:
----------------------------------------
Max, I think if cc for the project exists (situation 1) we need to add hibernate nature,
enable hibernate3 support and set existing cc as default for the project. Because if we
delete project X and create it again we'll found that cc X exists and will not enable
hibernate3 support and hibernate nature - this is wrong.
But if we uninstall jpa facet and install it again - automatic enable of hibernate3
support is wrong too...
From this too evils I choose automatic enable of hibernate nature and
hibernate3 support.
Problems with ConsoleConfiguration creation
-------------------------------------------
Key: JBIDE-3664
URL: https://jira.jboss.org/jira/browse/JBIDE-3664
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Hibernate
Affects Versions: 3.0.0.CR2
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Priority: Critical
Fix For: 3.0.0.GA
ConsoleConfiguration must be created in install facet (jpa) listener.
if cc for the project exists - do not override user changes(such as cc, hibernate nature,
hibernate3 support...)
If cc with project name exists(but not for this project), the name must be
"project_name (1)"
If cc for the project doesn't exist then hibernate nature, hibernate3 support must be
enabled and new cc set as default.
--
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