[jbosstools-issues] [JBoss JIRA] (JBIDE-10592) deployments tab war module deployment location is ignored

[Fred Bricon (JIRA)]

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

Fred Bricon commented on JBIDE-10592:
-------------------------------------

Rob, you can reproduce the issue by creating a new JavaEE Project from JBoss Central.
Once the projects are created, look at the  archiveNames in <project>-ear/.settings/org.eclipse.wst.common.component.
deploy the EAR project on AS7, the projects are deployed following the expected archiveName property :
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
    <wb-module deploy-name="multi">
        <wb-resource deploy-path="/" source-path="/target/m2e-wtp/ear-resources"/>
        <wb-resource deploy-path="/" source-path="/src/main/application" tag="defaultRootSource"/>
        <dependent-module archiveName="multi-web-0.0.1-SNAPSHOT.war" deploy-path="/" handle="module:/resource/multi-web/multi-web">
            <dependency-type>uses</dependency-type>
        </dependent-module>
        <dependent-module archiveName="multi-ejb-0.0.1-SNAPSHOT.jar" deploy-path="/" handle="module:/resource/multi-ejb/multi-ejb">
            <dependency-type>uses</dependency-type>
        </dependent-module>
    </wb-module>
</project-modules>
{code}

Now go to you AS instance deployment tab and check the deployment locations are different from the aforementioned archiveNames.
                
> deployments tab war module deployment location is ignored
> ---------------------------------------------------------
>
>                 Key: JBIDE-10592
>                 URL: https://issues.jboss.org/browse/JBIDE-10592
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.M5
>         Environment: Eclipse Indigo SR1
>            Reporter: erik van altena
>            Assignee: Rob Stryker
>            Priority: Minor
>             Fix For: 3.3.0.Beta1
>
>
> This bug report is created as per requested in this closed issue:
> https://issues.jboss.org/browse/JBIDE-10590
> I have a Mavenized project (m2eclipse, JBoss Tools Maven Integration) which I publish to a JBoss 7 runtime (standalone) by dragging it to the runtime instance. To work around the publish directory names not matching the maven pom configuration, I use the runtime deployment tab to override the directory names that the project modules are deployed under in the deployments folder of the server.
> (next part copy/pasted from original issue comments)
> But then I run into the next oddity: the settings for the war module seem to be ignored out of the box. The deployment tab mentions the war module as being deployed as 'app-web.war' while in fact it ends up in the deployments directory as 'app-web-1.0.0-SNAPSHOT.war', just like Maven would name it if you don't provide a finalName. However, as soon as I tab over the deployment locations and save the changes to the runtime configuration, upon full publish the web module gets the directory name as it is listed in the deployments tab.
> To be a little more specific: I get this behavior when I haven't made changes yet to the war entry in the deployment tab; the tab indicates the correct name but the result after publishing is wrong. When I then press tab to navigate to the deployment-location of the war, I don't change anything but I hit CTRL+S to save changes, upon full publish the name is then correct.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira