[arquillian-issues] [JBoss JIRA] (ARQ-697) Exception "Could not deploy to container" should report the real exception why the managed server is failing

[Geoffrey De Smet (Created) (JIRA)]

Exception "Could not deploy to container" should report the real exception why the managed server is failing
------------------------------------------------------------------------------------------------------------

                 Key: ARQ-697
                 URL: https://issues.jboss.org/browse/ARQ-697
             Project: Arquillian
          Issue Type: Enhancement
      Security Level: Public (Everyone can see)
            Reporter: Geoffrey De Smet
            Priority: Critical


Currently, when something goes wrong in a managed server, such as ARQ-660, you get a meaningless exception "Could not deploy to container".

The real exception should be reported, for example "port in use".

It's furthermore unclear, how far this "Could not deploy to container" stretches: if we have a bug in our CDI configuration (such as an Ambiguous dependency) in our war, will it also be reported as such or not?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira