[
https://issues.apache.org/jira/browse/MTOMCAT-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579183#comment-13579183
]
Olivier Lamy (*$^¨%`£) commented on MTOMCAT-206:
------------------------------------------------
no worries. It works fine locally too.
Looks to be some overload on the asf jenkins.
> Runtime dependencies within multi module projects are not loaded.
> -----------------------------------------------------------------
>
> Key: MTOMCAT-206
> URL: https://issues.apache.org/jira/browse/MTOMCAT-206
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: commons-lib
> Affects Versions: 2.0
> Reporter: Ludwig Magnusson
> Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.1
>
>
> I am not sure if this counts as a duplicate of MTOMCAT-46, there are some
> differences...
> Consider a multi module project in maven structured like this:
> - parent
> - api
> - implementation
> - webapp
> The webapp has a compile scope dependency on the API and a runtime scope
> dependency on the implementation. The implementation classes are loaded with
> some dependency injection framework.
> If I run tomcat(7):run in the root project it will fail because the tomcat
> plugin does not add the implementation classes (i.e. the runtime dependency)
> to the classpath. If I change the dependency scope of the implementation
> dependency to compile, it works.
> The solution for this was pretty simple. Just change one method call in
> DefaultClassLoaderEntriesCalculator, viewable in the applied patch. All tests
> and IT-tests still pass.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
