2011/9/9 <mike.wat...@comcast.net>:
> I am using: Tomcat 6.0.33
>
> In the catalina.properties file I have the following:
> shared.loader=/path/to/a/directory,${tomcat.additional.classpath}
>
> My issue is that "/path/to/a/directory" is added to the classpath, but the
> contents of ${tomcat.additional.classpath} are not.
>
> 'ps -eaf' does show -Dtomcat.additional.classpath=/path/to/another/directory,
> so I know the system property is being set correctly.
>
> Also, if I hard code
> shared.loader=/path/to/a/directory,/path/to/another/directory, this also
> works fine (note: This is not really an option-this additional-classpath
> stuff is added by our deployment automation for push-button deploys).
>
> This problem exists with common.loader & server.loader too.
>
> This problem does not exist in 5.5.33.
>
> Does anyone know why ${tomcat.additional.classpath} would not be expanded? Is
> there something special I need to enable under 6.0.33 to allow the classpath
> to be modified by a system property?
>
> Thanks for any help people can provide.
>
You can use only ${catalina.base} and ${catalina.home} there in Tomcat
5.5 and Tomcat 6.0.
In 7.0.17 and later you can use any other substitutions there, implemented as
https://issues.apache.org/bugzilla/show_bug.cgi?id=50677
This enhancement has not been backported to 6.0.
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
