It is necessary to ensure that src/main/webapp exists to ensure the
application starts with the Tomcat Gradle Plugin.
This commit adds a Manifest file to src/main/webapp/META-INF to ensure
that git contains the otherwise empty directory.
- Upgrade to 0.0.3.RELEASE of the plugin
- Declare a dependency in the springIoVersions configuration on the
Platform’s platform-versions artifact. An external property is used to
provide the version of this artifact. This means that the build script
does not need to refer to a snapshot artifact (the only version
available at the time of writing) and also breaks a circular
dependency between Spring Security (a project that’s part of the
Platform) and the Platform itself.
- The plugin applied and the libs-snapshot repository is added only
if the external property is specified. This removes the possibility
of a release or milestone being shipped with a snapshot dependency
(unless the release build is performed with -PplatformVersion=foo).
A number of projects had duplicate dependencies on their classpaths
as a result of the same classes being available in more than one
artifact, each with different Maven coordinates. Typically this only
affected the tests, but meant that the actual classes that were
loaded was somewhat unpredictable and had the potential to vary
between an IDE and the command line depending on the order in which
the aritfacts appeared on the classpath. This commit adds a number of
exclusions to remove such duplicates.
In addition to the new exclusions, notable other changes are:
- Spring Data JPA has been updated to 1.4.1. This brings its
transitive dependency upon spring-data-commons into line with
Spring LDAP's and prevents both spring-data-commons-core and
spring-data-commons from being on the classpath
- All Servlet API dependencies have been updated to use the official
artifact with all transitive dependencies on unofficial servlet API
artifacts being excluded.
- In places, groovy has been replaced with groovy-all. This removes
some duplicates caused by groovy's transitive dependencies.
- JUnit has been updated to 4.11 which brings its transitive Hamcrest
dependency into line with other components.
There appears to be a bug in Gradle which means that some exclusions
applied to an artifact do not work reliably. To work around this
problem it has been necessary to apply some exclusions at the
configuration level
Conflicts:
samples/messages-jc/pom.xml
