[
https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-13263:
-------------------------------------
attached patch for 4.0.1 does the following:
1) separate most logic into abstract class (so we don't have fix for as<6 be in as7
class)
2) resets the api used to one that works for LOCAL servers
3) disables scanner additions for remote servers
4) separates out the getInsideServer method in expectation of future api additions
We will implement a solution for remotes, whiuch may involve api enhancements, but not for
this patch. I'll link a related jira whne that happens.
Workspace metadata deployment does not work for AS 6
----------------------------------------------------
Key: JBIDE-13263
URL:
https://issues.jboss.org/browse/JBIDE-13263
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.Final
Environment: JBoss AS 6.1.0
Reporter: Martin Malina
Assignee: Max Rydahl Andersen
Priority: Critical
Fix For: 4.0.1.Final
Attachments: astools api.gliffy, astools api.png
When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the
module doesn't get deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira