You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Juan Jose Pablos <ch...@che-che.com> on 2004/05/27 11:45:13 UTC
Removing Jsp from distribution.
Hi,
I do not think that Forrest need JSP support for the run target. But
Jetty comes with it as default.
If I try to remove org.apache.jasper.jar I get a warning about a class
missing. Digging in the web I have found out that it would be possible
to remove with the modification of the way I have built Jetty.
Can I rebuild jetty-4.2.19.jar with these modifications?
Do we need JSP support for forrest?
Cheers,
Cheche
Re: Removing Jsp from distribution.
Posted by Juan Jose Pablos <ch...@che-che.com>.
Dave Brondsema escribió:
> I don't think we need JSP support, but how much work is it to rebuild
> jetty? Ideally we would just upgrade the jar file when there is a new
> jetty release, rather than taking time (and risk of mistake) by modifying
> it and rebuilding it.
>
We do not use a jar that comes out the box. We have to rebuild the jar
so it works with jdk 1.3
It is not much work, just comment it out a couple of lines on the
webdefault.xml file.
But hey!, that will save 240Kb for our project.
I am updating a wiki page here:
http://nagoya.apache.org/wiki/apachewiki.cgi?ForrestUpgradeLibs
Cheers,
Cheche
Re: Removing Jsp from distribution.
Posted by Dave Brondsema <da...@brondsema.net>.
On Thu, 27 May 2004, Juan Jose Pablos wrote:
> Hi,
>
> I do not think that Forrest need JSP support for the run target. But
> Jetty comes with it as default.
>
> If I try to remove org.apache.jasper.jar I get a warning about a class
> missing. Digging in the web I have found out that it would be possible
> to remove with the modification of the way I have built Jetty.
>
> Can I rebuild jetty-4.2.19.jar with these modifications?
>
> Do we need JSP support for forrest?
>
I don't think we need JSP support, but how much work is it to rebuild
jetty? Ideally we would just upgrade the jar file when there is a new
jetty release, rather than taking time (and risk of mistake) by modifying
it and rebuilding it.
--
Dave Brondsema : dave@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
http://csx.calvin.edu : student org