forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Closed: (FOR-404) Webapp and context:project/build/webapp/WEB-INF/logs/ folders
Date Mon, 06 Dec 2004 23:54:29 GMT

   The following issue has been closed.

   Resolver: Rick Tessner
       Date: Mon, 6 Dec 2004 5:53 PM

Resolved with SVN revision 110052.  Patched the ForrestLogTargetFactory java class.
View the issue:

Here is an overview of the issue:
        Key: FOR-404
    Summary: Webapp and context:project/build/webapp/WEB-INF/logs/ folders
       Type: Bug

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Forrest
             Launch servlet WAR
   Fix Fors:

   Reporter: Rick Tessner

    Created: Mon, 6 Dec 2004 12:20 PM
    Updated: Mon, 6 Dec 2004 5:53 PM
Environment: Linux, jdk 1.4.2_03, jetty 4.2.21

I'm having a rather odd problem that I just noticed this morning.  I was finding directories
called "context:" in various places throughout my system.

Looking at the contents of them, I found that they are being created a forrest webapp that
I run under jetty every once in a while.  Note that this is the webapp built by "forrest war"
and not from "forrest run".

The reason that I'm finding them in various places is that they're being placed in the directory
I happen to be cd'd to when I start jetty.

The directory structure I'm finding underneath this directory is:


and under there are the various logs that forrest produces.  Given the path under this "context:"
directory, it does appear that this is related to Forrest and not something else.

The WEB-INF/logkit.conf looks good.  It references ${context-root} as it should for the determining
the location of the logfiles.

This happens if I have the war file unzipped in it's own directory under the jetty/webapps
directory or if it just sits there as a .war file.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message