tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Loïc Guerrin (JIRA) <>
Subject [jira] [Commented] (MTOMCAT-173) Direct dependencies are not added to classpath
Date Mon, 22 Oct 2012 09:58:12 GMT


Loïc Guerrin commented on MTOMCAT-173:


I have the same issue with tomcat7-maven-plugin:2.0. But it's during an integration test with
junit. I have the structure below:

-- project-domain
-- project-webapp

The module project-domain isn't added to the classpath and the startup of the tomcat fails.
In the maven debug log I see too 'skip adding artifact project-domain as it's in reactors'.

In DefaultClassLoaderEntriesCalculator#calculateClassPathEntries at line 116, the method isInProjectReferences
rejects the project-domain as it's in projectReferences of project-webapp.

So is it possible to add a cheap workaround like a configuration parameter 'forceIncludeProjectReferences'
in order to add those project references to module classpath?


> 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
For more information on JIRA, see:

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

View raw message