[ https://jira.jboss.org/jira/browse/JBIDE-4374?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-4374: --------------------------------------- Fix Version/s: 3.1.0.M3 -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-4374?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-4374: --------------------------------------- Fix Version/s: 3.1.0.GA (was: LATER) I believe this is needed for solving the usecase of allowing to deploy specific jars to ode.war/web-inf/processes I believe or ? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-4374?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-4374: -------------------------------------------- Another usecase is being able to deploy to deploy.last folder. See http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247344#... -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-4374?page=com.atlassian.jira.plu... ] 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. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-4374?page=com.atlassian.jira.plu... ] Rob Stryker updated JBIDE-4374: ------------------------------- Attachment: JBIDE-4374.jpg what it looks like now -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-4374?page=com.atlassian.jira.plu... ] Max Rydahl Andersen reopened JBIDE-4374: ---------------------------------------- reopen for clarification/minor suggestions: 1) Looks overall good 2) Instead of Module Deployment just call it Deployment 3) Whether a server is ssh/ftp/local/etc. should probably not be as a tab, but as a combobox or radiobutton choice to control which settings are visible. (but that will become more obvious when we know what it will entail) 4) the paths looks all very loong - I assume your screenshot is all about absolute paths and not reletive ones ? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-4374?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-4374: -------------------------------------------- 1) Yes, the widgets and usecase are different so only one set of them should be visible. Having a tab per deploy method doesn't sound good... 2) path relative - cool 3) how can Tomcat WTP adapter have multiple pages that works and we dont ? if the page can't be persisted how are users supposed to use this ? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-4374?page=com.atlassian.jira.plu... ] Rob Stryker resolved JBIDE-4374. -------------------------------- Fix Version/s: 3.1.0.M3 (was: 3.1.0.GA) Resolution: Done resolving as fixed... works without wtp patch -- 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