[
https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi...
]
Michelle Murray updated JBIDE-13263:
------------------------------------
Writer: mmurray
Release Notes Text: By default, JBoss Application Server deployment scanners monitor
the workspace metadata for applications to deploy. API changes caused duplicate deployment
scanners to be created for JBoss Application Server 7. In rectifying this issue, tooling
modifications inadvertently caused no deployment scanners to be created for JBoss
Application Server 6. As a result, applications selected for deployment on JBoss
Application Server 6 failed to deploy. Modifications have been reworked to ensure a
deployment scanner is created for JBoss Application Server 6 and, consequently,
applications will deploy to JBoss Application Server 6. (was: Cause:Regression related to
support deployment for JBoss AS 7
Consequence: Workspace metadata deployment does not work for JBoss AS 6
Fix: Restores the workspace metadata deployment for JBoss AS 6
Result:Workspace metadata deployment works for JBoss AS 6)
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
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