[
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?
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: Max Rydahl Andersen
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