[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3664) Problems with ConsoleConfiguration creation

[Max Rydahl Andersen (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12451457#action_12451457 ] 

Max Rydahl Andersen commented on JBIDE-3664:
--------------------------------------------

I don't understand why you wouldn't enable hibernate3 support when there is an existing config with the same name - just create a new config with project_name (1)...
Optimally when deleting a project we should participate in that refactoring and ask if the console config should be deleted.

> 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