[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-9821) Wrong workflow when creating new example projects from Maven Archetypes

[Fred Bricon (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-9821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Bricon updated JBIDE-9821:
-------------------------------

    Description: 
If a user creates a Maven Archetype-based project example using the default example name (ex: jboss-javaee6-webapp6), then he can not create a 2nd example under a different name. A dialog box pops up and asks to overwrite (i.e delete) the existing jboss-javaee6-webapp6 project.
If the user answers yes, he loses his existing project, if he answers no, the project creation halts.

For archetype based projects, where the generated project name can be set by the user, the ImportMavenArchetypeProjectExample should not prevent the user from creating several projects based on the same example. The maven archetype wizard page has a built-in check that will prevent duplicate projects.

IMHO deleting project examples where the project name is variable doesn't make sense (as opposed to regular examples where the name cannot be changed) 

  was:
If a user creates a Maven Archetype-based project example using the default example name (ex: jboss-javaee6-webapp6), then he can not create a 2nd example under a different name. A dialog box pops up and ask to overwrite (i.e delete) the existing jboss-javaee6-webapp6 project.
If the user answers yes, he loses his project, if he answers no, the project creation halts.

For archetype based projects, where the generated project name can be set by the user, the ImportMavenArchetypeProjectExample should not prevent the user from creating several projects based on the same example. The maven archetype wizard page has a built-in check that will prevent duplicate projects.

IMHO deleting project examples where the project name is variable doesn't make sense (as opposed to regular examples where the name cannot be changed) 



> Wrong workflow when creating new example projects from Maven Archetypes
> -----------------------------------------------------------------------
>
>                 Key: JBIDE-9821
>                 URL: https://issues.jboss.org/browse/JBIDE-9821
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven, project-examples
>    Affects Versions: 3.3.0.M3
>            Reporter: Fred Bricon
>            Assignee: Fred Bricon
>             Fix For: 3.3.0.M4
>
>
> If a user creates a Maven Archetype-based project example using the default example name (ex: jboss-javaee6-webapp6), then he can not create a 2nd example under a different name. A dialog box pops up and asks to overwrite (i.e delete) the existing jboss-javaee6-webapp6 project.
> If the user answers yes, he loses his existing project, if he answers no, the project creation halts.
> For archetype based projects, where the generated project name can be set by the user, the ImportMavenArchetypeProjectExample should not prevent the user from creating several projects based on the same example. The maven archetype wizard page has a built-in check that will prevent duplicate projects.
> IMHO deleting project examples where the project name is variable doesn't make sense (as opposed to regular examples where the name cannot be changed) 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira