You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by "Arne Franken (JIRA)" <ji...@apache.org> on 2012/08/16 09:22:38 UTC
[jira] [Comment Edited] (MTOMCAT-173) Direct dependencies are not
added to classpath
[ https://issues.apache.org/jira/browse/MTOMCAT-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435809#comment-13435809 ]
Arne Franken edited comment on MTOMCAT-173 at 8/16/12 6:22 PM:
---------------------------------------------------------------
I'm using:
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
was (Author: arnefranken):
I'm using {{Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)}}
> Direct dependencies are not added to classpath
> ----------------------------------------------
>
> Key: MTOMCAT-173
> URL: https://issues.apache.org/jira/browse/MTOMCAT-173
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Components: tomcat6, tomcat7
> Affects Versions: 2.0
> Reporter: Arne Franken
> Assignee: Olivier Lamy (*$^¨%`£)
>
> in DefaultClassLoaderEntriesCalculator#calculateClassPathEntries, direct dependencies are not added, the log message says "skip adding artifact " + artifact.getArtifactId() + " as it's in reactors".
> In my case, it's a jar that is configured as a direct dependency. When the Webapp starts, the Jar is missing from the Classpath and the startup fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org