Forrest
  1. Forrest
  2. FOR-207

'forrest war' copies non-forrest files to war

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.6
    • Fix Version/s: 0.6
    • Component/s: Launch 'forrest'
    • Labels:
      None
    • Environment:
      MacOS X 10.3.4., Java 1.4.2

      Description

      When running 'forrest war' on a project, everything within that directory will be copied into the resulting war file, including files that live outside the src/directory. I happened to have a CVS version of the site parallel to src/, which included a backup of some rather largish files. The resulting war file weighed in at a whopping 58,8 Mb, with the expanded webapp approximating 100 Mb! It effectively killed the webapp (out-of-memory).

        Activity

        Hide
        Sjur N. Moshagen added a comment -
        I've attached a disk-usage (du) dump of the expanded webapp. Everything in Library/Tomcat/webapps/samsan2/project/cvs/ should be excempted from the war, as well as /Library/Tomcat/webapps/samsan2/project/war-arkiv.

        This bug did not exist under Forrest 0.5.1, and not under early versions of 0.6dev. I haven't been building wars using the 0.6 versions for a long time, so I can't really tell when the bug was introduced.
        Show
        Sjur N. Moshagen added a comment - I've attached a disk-usage (du) dump of the expanded webapp. Everything in Library/Tomcat/webapps/samsan2/project/cvs/ should be excempted from the war, as well as /Library/Tomcat/webapps/samsan2/project/war-arkiv. This bug did not exist under Forrest 0.5.1, and not under early versions of 0.6dev. I haven't been building wars using the 0.6 versions for a long time, so I can't really tell when the bug was introduced.
        Hide
        Nicola Ken Barozzi added a comment -
        This is done on purpose because in the next release all the project contents can be used to make documentation.
        It seems reasonable however to limit the copying to only the src dir, and I have set it for 0.6.
        Show
        Nicola Ken Barozzi added a comment - This is done on purpose because in the next release all the project contents can be used to make documentation. It seems reasonable however to limit the copying to only the src dir, and I have set it for 0.6.
        Hide
        Dave Brondsema added a comment -
        Limiting it to the ${project.content-dir} dir and the ${project.status} file makes sense to me.
        Show
        Dave Brondsema added a comment - Limiting it to the ${project.content-dir} dir and the ${project.status} file makes sense to me.

          People

          • Assignee:
            Unassigned
            Reporter:
            Sjur N. Moshagen
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development