[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4374) Modules / deployment page

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-4374:
------------------------------------

I believe SSH should be a tab as the SSH connection would probably involve all new widgets, such as server, username, password, root folder, etc. Having controls such as "workspace metadata" simply would not make sense there. 

Yes the paths are all absolute there. Paths such as "server/default/deploy" also work. 

I've also just remembered that though it's committed, the viewer-portion will not be persisted until this upstraem bug is fixed.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=286699

> Modules / deployment page
> -------------------------
>
>                 Key: JBIDE-4374
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4374
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: JBossAS
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 3.1.0.GA
>
>         Attachments: JBIDE-4374.jpg
>
>
> Create a Modules page in the server editor where you can specify the deployment location of each module you'll be deploying. This is due to the usecase where you need one module deployed to the default server location (for guaranteed early startup) but another to the separated metadata or custom location. 

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