[
https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi...
]
Paco Soberón commented on JBIDE-13263:
--------------------------------------
Same problem here: JBoss Tools 5.1.0.GA with latest version of JBoss Tools, Ubuntu 12.04,
x86_64.
My application is an EAR. Adding it to the server makes the 'physical' deployment,
i.e., the resources get copied to the destination folder in the workspace metadata.
However, the server doesn't seem to notice the change.
Strangely enough, it worked perfectly with the Beta1 version. It was yesterday, after
update to final version, that it stopped working.
The workaround (selecting the 'Use the JBoss deploy folder' option) did the trick
for me.
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