We could, but:
1. some architectures (One of my first beta testers is on MacOS X) do not seem to have the jar at all - it seems to have been collapsed into the rest of the runtime. 2. Many people will be running JBoss on a JRE not a JDK, and precompiling their JSPs during development. I am willing to work on run.sh to automatically add tools.jar to the classpath, if you will do the run.bat. I think the warning should remain though, although I don't like it, because people on JREs may not realize why their JSPs will not compile. What do you think ? Jules --- Peter Fagerlund <[EMAIL PROTECTED]> wrote: > > When the new ClassLoader code is checked in, I > shall > > work on a proper JSP solution. Until then, > everything > > is just a temporary hack. > > > > If you want JSP compilation to work, you have to > tell > > JBoss where the tools.jar is. We can't ship it > with > > JBoss because it is part of the JDK. > > Yes but can We not programatically add that > classpath at runtime ? since We > already have set a path:JAVA_HOME on our machines ? > ... > > /peter_f > ________________________________________________________________ Nokia 5510 looks weird sounds great. Go to http://uk.promotions.yahoo.com/nokia/ discover and win it! The competition ends 16 th of December 2001. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
