[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:
--------------------------------------
On
[dependency:tree|http://maven.apache.org/plugins/maven-dependency-plugin/t...]
v2.8 I found this
{code}
The scope to filter by when resolving the dependency tree, or null to include dependencies
from all scopes. Note that this feature does not currently work due to MNG-3236.
User property is: scope.
{code}
Indeed both of these produce the same output
{code}
[tdiesler@localhost example]$ mvn -Dtarget.container=wildfly800 dependency:tree
[tdiesler@localhost example]$ mvn -Dtarget.container=wildfly800 -Dscope=test
dependency:tree
{code}
The scope=test dependencies are however different at surefire runtime and include the old
marshalling-river version. This only shows with -X
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: Thomas Diesler
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