[jbosstools-issues] [JBoss JIRA] (JBIDE-15204) New Project wizard hangs when an invalid package is provided as input.

[Gerry Matte (JIRA)]

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

Gerry Matte commented on JBIDE-15204:
-------------------------------------

For my case, my Developer Studio workspace is at c:\d\Workspace-Juno 
and my command was new-project --named threestar --topLevelPackage ca.gerrymatte.threestar ;

It appears that the generation of a project folder structure proceeds without error.  However, the 'Importing Forge Project' step opens an eclipse "Problem Occurred" window with the error: 
Invalid project description.
OK
c:\d\Workspace-Juno\threestar overlaps the location of another project: 'threestar'

I don't believe this error has anything to do with the package name.  The disk folder structure actually created complies with the topLevelPackage value noted above.  

I suspect this is an error message that should not be triggered and it's possible to carry on working with forge.  However, I don't know if my new project should have been imported into eclipse.  In earlier forge versions, I executed from a DOS window rather than from within eclipse.



                
> New Project wizard hangs when an invalid package is provided as input.
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-15204
>                 URL: https://issues.jboss.org/browse/JBIDE-15204
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: forge
>    Affects Versions: 4.1.0.Beta2
>            Reporter: Vineet Reynolds
>         Attachments: eclipse-threaddump-1373927608559.tdump, forge-threaddump-1373927611426.tdump
>
>
> The new project wizard hangs when an invalid package name (according to Forge) is provided in the dialog box. On clicking the Finish button in the wizard, it hangs when running the {{new-project ....}} Forge command.
> This is due to Forge waiting for the user to supply a valid package name. See attached thread dumps.
> Other comments:
> In a way, this is related to FORGE-687, but the fix should probably go into the wizard so users can correct the name instead of Forge deciding on a default.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira