]
Jeff MAURY updated JBIDE-18525:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.x)
Investigate how to do module deployment ordering properly with
management api
-----------------------------------------------------------------------------
Key: JBIDE-18525
URL:
https://issues.jboss.org/browse/JBIDE-18525
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.2.0.CR2
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.5.0.AM1
This is a followup of JBIDE-18373 which was originally about deployment via management
api not handling "mark as deployable" files properly. This was fixed, but
there's still a problem of ordering. The use case here was a seam project deployed to
EAP 6.3. There are three parts:
1. Seam project war
2. database driver jar
3. datasource xml
When you click "Add and Remove..." on the server in server view, it will
sometimes be deployed in the wrong order and fail to deploy.
Specifically, when you click "Add All" in the dialog, it will not work, whereas
if you click "Add" for each of the three resources, it will deploy alright.
As Rob pointed out, it can get really tricky to guess the right ordering.
See JBIDE-18373 for more details.