[
https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-19641:
-------------------------------------
I have a strong suspicion that the wf9 jars "working for all cases" can't
possibly include working for as7x... since remoting and other libs have actually gone up
major versions in that time. (remoting, for example, up from 3.2.x to 4.0.x). The
reason we split up the clients into 7x vs wf was just because of these changes in
remoting, if I recall correctly.
Let's not forget, if this bug is 100% on the client side, you *could* just do an
off-cycle release of a specific jar, not to be published to any EAP, but just for us to
consume directly. All you'd need to do is put it somewhere accessible via maven so
that we can pull it in.
Big war deployment via management API gets stuck
------------------------------------------------
Key: JBIDE-19641
URL:
https://issues.jboss.org/browse/JBIDE-19641
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.0.Alpha2
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.3.0.Beta2
Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log,
stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log
When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it
will not go through.
This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually
used that JIRA to fix a side issue - the stuck operation could not be canceled.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)