[
https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi...
]
Martin Malina edited comment on JBIDE-13263 at 12/11/12 9:48 AM:
-----------------------------------------------------------------
You're right, I can confirm this issue applies to JBoss AS 5.1.0.GA as well :( And
same for JBoss EAP 5.1.2 but EAP at least defaults to JBoss deploy folder so you don't
see this issue unless you change deployment to workspace metadata.
was (Author: mmalina):
You're right, I can confirm this issue applies to JBoss AS 5.1.0.GA as well :( And
same for JBoss EAP 5.1.2
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: Rob Stryker
Fix For: 4.0.1
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