[
https://issues.jboss.org/browse/JBIDE-17172?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-17172.
---------------------------------
Resolution: Done
Fixed. We now first check the module state before doing the remove. If the remote module
exists on the remote server, we do the remove.
This will increase (slightly) the time it takes to publish via mgmt, sadly, since it's
now 3 remote calls instead of 2. (check state, remove, add).
Deployment to WildFly 8 shows errors when using management api
--------------------------------------------------------------
Key: JBIDE-17172
URL:
https://issues.jboss.org/browse/JBIDE-17172
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta1
Reporter: Martin Malina
Assignee: Rob Stryker
Priority: Critical
Fix For: 4.2.0.Beta2
Attachments: error-view.png, server-view.png
When you try to deploy to a WildFly 8.0 or 8.1 server using the management api profile,
you get errors:
{code}
!ENTRY org.jboss.ide.eclipse.as.core 4 1644298251 2014-04-22 15:55:00.287
!MESSAGE Deployment of module dynproj has failed
!SUBENTRY 1 org.jboss.ide.eclipse.as.management.wildfly8 4 0 2014-04-22 15:55:00.287
!MESSAGE The operation REMOVE was not executed on unit dynproj.war
!SUBENTRY 1 unknown 0 0 2014-04-22 15:55:00.287
!MESSAGE OK
{code}
!error-view.png!
Note that the project actually gets deployed, but the server view will show [Republish]
next to the module.
!server-view.png!
As a consequence of this, the module will actually stay deployed even if you remove it in
the server view.
--
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