[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-7614) Add third column to deployment page to rename the output file / folder.

[Rob Stryker (JIRA)]

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

Rob Stryker updated JBIDE-7614:
-------------------------------

    Attachment: JBIDE-7614.patch


Patch to trunk for this. The solution here changes the first column to force you to append the output name of the deployment. It has sensible defaults so if the attribute is null, it will use an API to get the default one.

Publisher and UI obviously use same API to discover deploy path. 

> Add third column to deployment page to rename the output file / folder. 
> ------------------------------------------------------------------------
>
>                 Key: JBIDE-7614
>                 URL: https://issues.jboss.org/browse/JBIDE-7614
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: JBossAS
>    Affects Versions: 3.2.0.Beta1
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 3.2.1
>
>         Attachments: JBIDE-7614.patch
>
>
> Currentlyu you can only update what folder a deployment goes to but you cannot at the last minute rename a deployment. Adding this third column should allow renaming of the final deployment.
> This will also be a good time to find any and all places (like explore utils) that do NOT use the proper API to find out based on settings where a module should be deployed to (or undeployed from). 
> Test this heavily and don't break shit...

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