[
https://issues.jboss.org/browse/JBIDE-11036?page=com.atlassian.jira.plugi...
]
Martin Malina updated JBIDE-11036:
----------------------------------
Workaround Description:
For a workaround, edit $JBOSS_DEST/standalone/configuration/standalone.xml, look for
<deployment-scanner and change the line from:
<deployment-scanner path="deployments"
relative-to="jboss.server.base.dir" scan-interval="0"/>
to:
<deployment-scanner path="deployments"
relative-to="jboss.server.base.dir" scan-interval="5000"/>
Then restart the server in JBoss Tools.
Deployment on EAP 6.0.0 ER1 not working out of the box
------------------------------------------------------
Key: JBIDE-11036
URL:
https://issues.jboss.org/browse/JBIDE-11036
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.Beta1
Environment: jbdevstudio-product-universal-5.0.0.v201202221611M-H70-Beta1.jar
JBoss EAP 6.0.0 ER1
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 3.3.0.Beta1
By default, the deployment scanner in ER1 is set to interval 0, effectively disabled.
Not sure if this will be the default for all future EAP versions.
Therefore when you deploy to this server in JBoss Tools, it doesn't get deployed.
I don't know if/how we can fix this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira