tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivier Lamy (*$^¨%`£) (JIRA) <>
Subject [jira] [Commented] (MTOMCAT-173) Direct dependencies are not added to classpath
Date Mon, 20 Aug 2012 12:24:38 GMT


Olivier Lamy (*$^¨%`£) commented on MTOMCAT-173:

I miss you here ! 
Don't clean your projects and you won't rebuild/recompile everything.
use only mvn -pl :dep-issue-webapp tomcat7:run (without -am) if you don't want to rebuild/recompile
> 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