See the light - agile, industrial strength, rapid web application development made easy

(Quick Reference) # 4.7.5 Providing Default Dependencies - Reference Documentation Authors: Graeme Rocher, Peter Ledbrook, Marc Palmer, Jeff Brown, Luke Daley, Burt Beckwith, Lari Hotari Version: 2.3.8 ## 4.7.5 Providing Default Dependencies Most Grails applications have runtime dependencies on several jar files that are provided by the Grails framework. These include libraries like Spring, Sitemesh, Hibernate etc. When a war file is created, all of these dependencies will be included in it. But, an application may choose to exclude these jar files from the war. This is useful when the jar files will be provided by the container, as would normally be the case if multiple Grails applications are deployed to the same container. The dependency resolution DSL provides a mechanism to express that all of the default dependencies will be provided by the container. This is done by invoking the `defaultDependenciesProvided` method and passing `true` as an argument:

    grails.project.dependency.resolution = {    defaultDependenciesProvided true // all of the default dependencies will
                                         // be "provided" by the container    inherits "global" // inherit Grails' default dependencies    repositories {
            grailsHome()
            …
        }
        dependencies {
            …
        }
    }
`defaultDependenciesProvided` must come before `inherits`, otherwise the Grails dependencies will be included in the war. | Quick Reference (hide)