Grails
  1. Grails
  2. GRAILS-3697

grails.war.dependencies documentation problem

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.0.4
    • Fix Version/s: None
    • Component/s: Documentation
    • Labels:
      None
    • Environment:
      all

      Description

      (from post to grails user group http://www.nabble.com/grails.war.dependencies-documentation-problem-td20956861.html)

      the grails user guide states that "you can explicitly specify the
      complete list of libraries to include in the WAR file by setting the
      properties grails.war.dependencies " - this is exactly the facility i
      need to create "svelte" war files containing none of the grails dist
      or lib jars - however, it turns out that the grails dist jars are
      included anyhow - taking a look at the War script, it's clear that
      this is intentional, not a bug - so that means that the documentation
      is incorrect - i'll file a jira if you concur

      in order to work-around this problem, i'm using grails.war.resources
      to delete the grails lib jars from the staging dir - it's all rather
      hacky and it would be nice if there was a cleaner way to control what
      goes into a war file

      in case you are wondering why in the world i'd want to strip all the
      grails lib and dist jars from my war file: i'm deploying many grails
      apps to my container (like on the order of 10-20) - this is because i
      am taking advantage of the application composition facility provided
      by SIP servlet 1.1 containers like SailFin and each of my apps combine
      both SIP (ECharts for SIP servlets) and grails elements - this may
      sound like a niche requirement but i also see that the grails support
      in GlassFish 3.0 includes a special script that generates a svelte war

      • in other words, the Glassfish developers also realized that there
        was no easy way to strip the grails jars from the war so they decided
        to write their own script - so perhaps this is the answer: add a new
        "SkinnyWar" script to the grails distro

        Activity

        Hide
        Graeme Rocher added a comment -

        Assigning all documentation related issues to 1.2 final since they don't represent a change to the codebase

        Show
        Graeme Rocher added a comment - Assigning all documentation related issues to 1.2 final since they don't represent a change to the codebase

          People

          • Assignee:
            Unassigned
            Reporter:
            Gregory W. Bond
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Last Reviewed:

              Development