tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arne Franken (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MTOMCAT-173) Direct dependencies are not added to classpath
Date Fri, 17 Aug 2012 10:06:37 GMT

    [ https://issues.apache.org/jira/browse/MTOMCAT-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436637#comment-13436637
] 

Arne Franken commented on MTOMCAT-173:
--------------------------------------

I just found what the problem is:

I created a new project using your archetype. Example directory structure:
dep-issue-api/
dep-issue-api-impl/
dep-issue-webapp/
dep-issue-webapp-exec/
dep-issue-webapp-it/

I usually build and start all modules from the projects root directory, in this case:
mvn -am -pl dep-issue-webapp clean install && mvn -pl dep-issue-webapp tomcat7:run

if I start the tomcat plugin this way, all direct dependencies of the dep-issue-webapp module
will not be added to the classpath by Maven, the startup of the webapp will fail.

---------

If I instead do this:
mvn -am -pl dep-issue-webapp clean install
cd dep-issue-webapp
mvn tomcat7:run

Maven will add all direct dependencies to the classpath and the webapp will start correctly.
                
> 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


Mime
View raw message