tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arne Franken (JIRA)" <>
Subject [jira] [Commented] (MTOMCAT-173) Direct dependencies are not added to classpath
Date Mon, 20 Aug 2012 11:26:38 GMT


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
> Direct dependencies are not added to classpath
> ----------------------------------------------
>                 Key: MTOMCAT-173
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message