[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-4630) Maven parent project created under workspace even when alternate location specified in New -> Seam Web Project wizard

[Denis Golovin (JIRA)]

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

Denis Golovin updated JBIDE-4630:
---------------------------------

    Fix Version/s: 3.1.0.M3


> Maven parent project created under workspace even when alternate location specified in New -> Seam Web Project wizard
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-4630
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4630
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 3.1.0.M2
>         Environment: Windows XP, Eclipse 3.5
>            Reporter: Tim Schwenk
>            Assignee: Snjezana Peco
>            Priority: Minor
>             Fix For: 3.1.0.M3
>
>
> When creating a Seam project using the New->Seam Web Project wizard, it is possible to select a location outside the workspace directory to create the project(s).  If you select the Maven facet, the wizard creates POMs for the typical war, ear, ejb, and test projects, and in addition it creates a parent project with basically just a parent POM.  Everything works great in Eclipse, and the projects deploy to a JBoss test server perfectly - needless to say I was thrilled with this.  However, when I decided to drop to the command line and run a Maven build outside Eclipse, I realized that the parent project was created in the workspace directory rather than alongside the other projects.
> Fortunately, there is a simple way to resolve this problem:  Just copy the parent project to the desired location (alongside the other projects), delete the project from Eclipse, and use the "File->Import->Existing Projects Into Workspace" feature to open the parent project form its new location.  If automatic builds are disabled, a refresh/clean/build may be necessary to get everything compiled correctly again.  After that, everything works properly, and it's also possible to build everything by executing 'mvn package' from inside the parent project directory.

-- 
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