[jboss-jira] [JBoss JIRA] (WFLY-920) Module Service Dependencies do not take transitive dependencies into account

Tue May 7 12:22:53 EDT 2013

    [ https://issues.jboss.org/browse/WFLY-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12772796#comment-12772796 ] 

David Lloyd commented on WFLY-920:
----------------------------------

If we use the aforementioned dependency mapping algorithm, we could make intra-deployment module dependencies all be optional, which would allow us to tolerate missing JARs.

> Module Service Dependencies do not take transitive dependencies into account
> ----------------------------------------------------------------------------
>
>                 Key: WFLY-920
>                 URL: https://issues.jboss.org/browse/WFLY-920
>             Project: WildFly
>          Issue Type: Bug
>          Components: Class Loading
>            Reporter: Stuart Douglas
>            Assignee: Stuart Douglas
>
> A ModuleLoadService has dependencies on all its dependent ModuleSpecServices, however this does not work if the ModuleSpecService has a dependency on another ModuleSpecService with export=true, as the module may attempt to load before transitive dependencies have been started.
> This has caused transient failures in EarClassPathTransitiveClosureTestCase.

--
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