[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=12481254#action_12481254 ] 

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

I'm not really sure how to interpret this stuff actually.  For example, on page 1, if the deploy location is set to metadata, then blank should be the metadata folder (aka the current default deploy folder) but then any paths relative to that do not make sense at all as they could muck up the metadata folder structure by going ../otherServer/asfasdf  whatever. So paths relative to metadata do not make sense.

On the other hand if the paths are relative to the server location then that means there's no way to explicitly signal to use the server's default location. For example, imagine the server's absolute default is the metadata location (/home/rob/apps/eclipseWorkspace/.metadata/.plugins/etcetcetc) and the user has 2 possible modules to deploy. One he wants to go to server/default/deploy, the other he wants to go to the default metadata location.

If "" means stay with the server's default, then logically "server/default/deploy" would actually resolve to /home/rob/apps/eclipseWorkspace/.metadata/.plugins/etcetcetc/server/default/deploy, which is simply wrong. 

So since:
  1) paths relative to metadata do not make sense, and
  2) we need a way to signify use the servers default

I'd suggest  "" should mean use the server's default deploy location, whether that be metadata or some custom folder somewhere. On the other hand, any string OTHER than the empty string should be server relative (so server/default/deploy  or server/{jboss_config}/deploy  would still resolve properly, and blank would be the equivilent of no customization). 

It's the only solution I can come up with honestly that stops users from making metadata-relative paths while still allowing full filesystem paths and while still making it easy for server-relative paths. 

> Modules / deployment page
> -------------------------
>
>                 Key: JBIDE-4374
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4374
>             Project: JBoss Tools
>          Issue Type: Feature Request
>          Components: JBossAS
>            Reporter: Rob Stryker
>            Assignee: Rob Stryker
>            Priority: Critical
>             Fix For: 3.1.0.GA
>
>
> 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