[
https://issues.jboss.org/browse/WFLY-4828?page=com.atlassian.jira.plugin....
]
jaikiran pai commented on WFLY-4828:
------------------------------------
{quote}
When module X is loaded to be used, it fails to be loaded, which is expected as well, but
the failure message is: "module X is not found", in fact it should be
"module X can not be loaded, because dependent module Y is not found".
{quote}
Can you attach an application which reproduces this exception?
Server starts when new module contains wrong dependency
-------------------------------------------------------
Key: WFLY-4828
URL:
https://issues.jboss.org/browse/WFLY-4828
Project: WildFly
Issue Type: Bug
Components: Server
Reporter: Hayk Hovsepyan
Assignee: Jason Greene
When there is dependency to non existing modules in a new added module configuration
file, server starts without any problem. But should fail.
The same non existent dependency added into existing modules configurations, causes
server to not start and appropriate errors are shown.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)