]
Ondrej Zizka resolved ARQ-697.
------------------------------
Resolution: Done
Fixed by
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".
Furthermore, the message is unclear: how far does this "Could not deploy to
container" message stretch? If we have a bug in our CDI configuration (such as an
Ambiguous dependency) in our war, will it also be reported with this exception or not?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: