[
https://issues.apache.org/jira/browse/MTOMCAT-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) closed MTOMCAT-59.
-----------------------------------------
Resolution: Not A Problem
> catalina.properties and catalina.policy are ignored
> ---------------------------------------------------
>
> Key: MTOMCAT-59
> URL: https://issues.apache.org/jira/browse/MTOMCAT-59
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: Maven 2.2.1, Tomcat 6.0.20
> Reporter: Torben Knerr
> Labels: tocheck
>
> Any configuration that is done in {{catalina.properties}} or
> {{catalina.policy}} is not considered when Tomcat is started via the
> tomcat-maven-plugin. I have tried to pass the system property
> {{-Dcatalina.config=/path/to/catalina.properties}}, but it is actually never
> read in the plugin code.
> The reason seems to be that in {{AbstractRunMojo.java}} the Tomcat container
> is created using
> {code}
> ...
> container = new Catalina();
> ...
> {code}
> When starting Tomcat manually using {{catalina.bat/sh}}, the container is
> started via
> {{[Bootstrap.java|http://www.docjar.com/html/api/org/apache/catalina/startup/Bootstrap.java.html]}}
> which -- in addition to creating a new Catalina instance -- reads and
> processes the two above mentioned files. In our special case we are relying
> on the {{shared.loader=/path/to/shared/libs/*.jar}} configuration in
> {{catalina.properties}}.
> Is this a known/intended issue? Is this something that we can hope for a fix
> in a future version?
> Cheers and kind regards,
> Torben
>
--
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
