[jboss-jira] [JBoss JIRA] (WFLY-2020) ARQ container cannot fetch deployment from client side any more
[
https://issues.jboss.org/browse/WFLY-2020?page=com.atlassian.jira.plugin....
]
Thomas Diesler commented on WFLY-2020:
--------------------------------------
This seems to be the offending commit
{code}
[tdiesler@localhost wildfly]$ gti bisect bad
a0c7edb142b75d92276fb9fa9c0033ea1d583934 is the first bad commit
commit a0c7edb142b75d92276fb9fa9c0033ea1d583934
Author: David M. Lloyd <david.lloyd(a)redhat.com>
Date: Thu Aug 29 22:45:30 2013 -0500
Update to JBoss Modules 1.4.0.Final
:100644 100644 c68f9aad334c782717006fe565923c27c888a341
1806df7fa4879bfb352f212ab636d2f17fec2c5e M pom.xml
:040000 040000 7c4309e8f415c07cd37bbb28d621c9e6f5f2d6ee
fddb9490d9cacf4cd8fed298dbad5fc662bdff05 M server
{code}
ARQ container cannot fetch deployment from client side any more
---------------------------------------------------------------
Key: WFLY-2020
URL: https://issues.jboss.org/browse/WFLY-2020
Project: WildFly
Issue Type: Bug
Reporter: Thomas Diesler
Assignee: Darran Lofthouse
Priority: Blocker
Fix For: 8.0.0.Beta1
This is likely due to a change in the JMX layer. All tests fail here
{code}
@ArquillianResource
public Deployer deployer;
InputStream input = deployer.getDeployment(BUNDLE_A);
{code}
AFAICS, there is only plain ARQ and JMX code involved.
--
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