[ https://issues.jboss.org/browse/JBIDE-7614?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-7614: ------------------------------- Fix Version/s: 3.2.1 (was: 3.2.0.CR1) push back -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7614?page=com.atlassian.jira.plugin... ] 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. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7614?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-7614: -------------------------------------------- Can I avoid having to specify the name and just let it use the API to get it ? That is how it worked before afaics. How does this work with publishers like the BPEL that sets the name with a version/timestamp ? And I understood it correct that it also fixes Fred's issue about actually listening to the API for the deployment name? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7614?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-7614: -------------------------------------------- forgot to assign back when commenting. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7614?page=com.atlassian.jira.plugin... ] Rob Stryker commented on JBIDE-7614: ------------------------------------ Yes Fred... as mentioned in the bugzilla, your problem is a complex mix of jeetools and servertools. I'm not sure it requires API changes, but, I did fiddle with that stuff once nad it ends up breaking dozens of wtp tests... Max: You do not need to specifically type in a deploy name. The API populates the UI with the default for you. The question here is whether it's ok to put it into two columns, or if I require the creation of a third. As for things like BPEL... well... I guess the UI breaks down there, but I can't think of any way to handle all use cases and still solve the major one. Seriously... I've racked my brain for excessive periods of time over the past year and cannot come up with a single UI to handle outlying cases like BPEL. In the BPEL case, the publisher chooses to ignore information set in some models. The publisher has the last final say on what to do and it chooses to ignore certain options. The entire case of the BPEL situation really messes up any possibility for a uniform UI. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7614?page=com.atlassian.jira.plugin... ] Rob Stryker resolved JBIDE-7614. -------------------------------- Release Notes Text: The UI for the Server editor, page 2 (deployment) will now display three columns named "Module", "Deployment Location", and "Temporary Deploy Path". The behaviour of columns 1 and 3 are unchanged, specifically, column 1 lists the module, and column three lists the folder you want to use as your temporary folder for that module. Column 2's behaviour has changed. Originally it would appear blank, and behave similarly to the Temporary Deploy Directory, except as the final location of the deployment. Now, it will default to display the output filename of the deployment (DynProj.war). Given a "Deploy Directory" (top of the page) of "/home/rob/tmp", the following "Deployment Location" values have the following effects: 1) SomeProj.war (output will be placed in /home/rob/tmp/SomeProj.war) 2) SomeProj3.war (output will be placed in /home/rob/tmp/SomeProj3.war) 3) folder/SomeProj.war (output will be placed in /home/rob/tmp/folder/SomeProj.war) 4) /home/somewhere/else/SomeProj.war (output will be placed in /home/somewhere/else/SomeProj.war) Resolution: Done -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-7614?page=com.atlassian.jira.plugin... ] Martin Malina closed JBIDE-7614. -------------------------------- I believe the feature behaves as expected. Verified in jbdevstudio-product-eap-macosx-cocoa-4.1.0.v201105041030R-H368-M1.jar . -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira