Make fields final where appropriate
Add class-level Javadoc
Replace PostViewFactory with static PostView methods
Optimize imports globally
Format sources globally
Reduce visibility where appropriate
Add class-level Javadoc for sagan.docs.support.*
Add class-level Javadoc for sagan.projects.support.*
Add class-level Javadoc for sagan.search.support.*
Add class-level Javadoc for sagan.projects.nav.*
Rename Nav{Section=>igation}, introduce Section enum
Move sagan.{support.nav=>blog.support}.SiteUrl
Add class-level Javadoc for sagan{|.team|.tools}.*
Add min-height so table doesn't break when downloads only have 1 row
Merge pull request #398 from spring-io/fix-tools-download-table-vertical-sizing

Add min-height so table doesn't break when downloads only have 1 row
Document and refactor sagan.support.nav.*
Add class-level Javadoc for sagan.blog.support.*
Add class-level Javadoc for sagan.blog.*
Merge pull request #327 from spring-io/doc

Add class-level Javadoc to sagan-site production classes
Prevent sagan-common from having Spring 3.2.x on its classpath

Spring Social GitHub has a transitive dependency on spring-webmvc
3.2.x. In the absence of any other spring-webmvc dependency, this
causes a mixture of Spring 3.2.x and Spring 4.0.x to be on
sagan-common's classpath.

This commit adds an explicit dependency on spring-webmvc. No version
number is specified to allow the version to be determined by the
Spring Boot plugin.

An alternative approach would be to use a resolution strategy:

configurations.all {
    resolutionStrategy {
        eachDependency {
            if (it.details.requested.group == 'org.springframework') {
                details.useVersion '4.0.5.RELEASE'
            }
        }
    }
}

Unfortunately, this approach requires you to specify the version of
Spring that you want to use, thereby preventing you from automatically
using the version that's provided by the Spring Boot plugin. There's
an issue open (spring-projects/spring-boot#932) to make the versions
available as properties, but, until that functionality is available,
I think the change made in this commit is the best solution.