On 18/11/2010 14:40, Thangalin wrote:
> Hi,
>
> Here's the situation, then.
There are ways to do what you are trying to do but the dev list is not
the place for that discussion. Please move this discussion to the users
list.
Mark
-
Hi,
Here's the situation, then.
The iReport tool (and hence JasperReports) bundles scores of JAR files
across two different directories. (One of these JAR files conflicts with a
JAR file deployed by Tomcat.)
For development purposes it makes sense to have Tomcat and iReport installed
on the same
> From: Thangalin [mailto:thanga...@gmail.com]
> Subject: setclasspath vs. setenv
> I find it odd that nowhere in that file is the classpath environment
> variable actually set.
That's because the CLASSPATH environment variable is inherently evil. Don't
ever use it (goes double for Tomcat). A
2010/11/17 Thangalin :
> Hi,
>
> Judging by its name alone, I would have thought that "setclasspath" (.bat or
> .sh) would be a place to put custom code that sets the classpath before
> Tomcat starts, or stops.
>
Setting CLASSPATH explicitly is a bad idea.
The cases when it is needed in Tomcat ar
On 17/11/2010 20:35, Thangalin wrote:
> Hi,
>
> Judging by its name alone, I would have thought that "setclasspath" (.bat or
> .sh) would be a place to put custom code that sets the classpath before
> Tomcat starts, or stops.
>
> I find it odd that nowhere in that file is the classpath environmen
