[
https://issues.apache.org/jira/browse/MTOMCAT-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555387#comment-13555387
]
Ludwig Magnusson commented on MTOMCAT-46:
-----------------------------------------
I encountered this error as well when I had a multi module project and my war
project had a runtime dependency to another module. The dependency was not
included when executing tomcat:run which it should be, they are included in the
packaging right? Although I agree that provided scope dependencies should not
be included.
> Plugins tomcat:run and tomcat:run-war are not loading the Provided and
> Runtime dependencies.
> --------------------------------------------------------------------------------------------
>
> Key: MTOMCAT-46
> URL: https://issues.apache.org/jira/browse/MTOMCAT-46
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
> Affects Versions: 1.0-beta-1
> Reporter: Bernardo Gomez Palacio
> Labels: notabug
>
> User Story: Developers checkout a Web Application from our SCM
> Repository(SVN) and through the tomcat:run (or tomcat:run-war) plugin can
> bootstrap and start a Tomcat Server and test the Web Application locally
> without even having Tomcat instances previously deployed either locally or
> remotely.
> To fulfill such User Story I started with the tomcat:run plugin but had
> issues with the Provided and Runtime dependencies. I then jumped to the
> tomcat:run-war using my own tomcat configuration files but had similar
> issues. I see that the tomcat:run-war plugin doesn't create a ClassLoader for
> the Catalina container in a similar way Tomcat's Bootstrap class does. I
> downloaded the code of the tomcat plugin and I am working in the fix but I
> need to share some thoughts about this...
> Approach A) Use a similar schema as the Tomcat Bootstrap in the Run*Mojos,
> let the developer provide those dependencies through the
> dependency:copy-dependencies to lets say target/tomcat/lib and load them from
> there. So the User controls what is deployed in lib.
> Approach B) Use a similar schema as the Tomcat Bootstrap in the Run*Mojos,
> the dependencies will be fetched using the dependencies defined in the
> pom.xml file (including transitive dependency resolution) and added to the
> ClassLoader.
> Thoughts and ideas are welcomed.
--
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: 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
