[ https://issues.jboss.org/browse/ISPN-2326?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-2326: ------------------------------------- Actually after careful reading of maven user guide this is not a bug. Their docs warn about unpredictable results if a dependency is included transitively via multiple paths. In this case c3p0 dependency appears twice, jdbc cachestore module depends on it in compile scope and lucene-directory in test scope. Only the fist dependency path is considered by assembly plugin. And if the first one happens to have 'test' scope that means the dependency won't make it into the final assembly. That's why the order of modules matters. Unfortunately changing the order of modules can fix c3p0 but leads to other deps being ignored, so we're not solving anything this way. We'll have to ask a maven guru. -- 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