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

[erik van altena (JIRA)]

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

erik van altena commented on JBIDE-10592:
-----------------------------------------

I would also want to raise a question of documentation based on this. If you want reliable results using JBoss Tools in a Mavenized project, it is really necessary that you provide a proper finalName for all Maven modules in the pom to circumvent this and other deployment issues. In fact it is highly necessary that you have your pom configuration clean and proper, or else m2eclipse might wrongly setup the Eclipse project facets to a point where JBoss Tools is also influenced:

https://issues.jboss.org/browse/JBIDE-10591

Perhaps the JBoss Tools documentation should have a document on Maven usage with best practices. For example, Jboss Tools has a Maven integration module, yet I don't see an entry in the reference guide for it yet:

http://download.jboss.org/jbosstools/nightly-docs/
                
> 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