[
https://issues.apache.org/jira/browse/MTOMCAT-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437792#comment-13437792
]
Arne Franken commented on MTOMCAT-173:
--------------------------------------
mvn -pl :dep-issue-webapp -am tomcat7:run
that actually works, but it means that I would ALWAYS have to build the webapp
and ALL dependencies before I can start it.
That may not be a problem in a small test project like the one the archetype
creates, but this is a big problem in a project where I have lot of
dependencies with (tens of) thousands of lines of code that have to be compiled
over and over again if I just want to restart my webapp.
> 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-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
