[
https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-19641:
-------------------------------------
At this time, we only have two sets of client jars: an as7x/eap6x stream, and a wildfly
stream. So if our final set of jars was from eap64, for example, we'd expect it to
work all the way back to 7.x.
Of course if it was absolutely impossible, we could work around it and split it into one
set for as7x and another set for eap6x. It wouldn't be a huge change, but it's
not our first choice if you happen to have jars that work back to as7x ;) But if
that's what you recommend, I could start to move the pieces so that we have a as7x /
eap6x split in client code.
Timing? I think our final is usually in the early winter. CR1 is in September, and thats
when new features stop getting added.
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)