Add licence and notice to all artifacts

- remove the epl-license; we haven't had an erlang module since 1.4

**cherry-pick to 2.0.x, 1.7.x**

(cherry picked from commit f3b977d)

# Conflicts:
#	build.gradle

Author: garyrussell

build.gradle

@@ -195,6 +195,16 @@ subprojects { subproject ->
 		archives javadocJar
 	}
 
+	jar {
+		from("${rootProject.projectDir}/src/dist") {
+			include "license.txt"
+			include "notice.txt"
+			into "META-INF"
+			expand(copyright: new Date().format("yyyy"), version: project.version)
+		}
+	}
+
+
 	build.dependsOn jacocoTestReport
 
 }

src/dist/epl-license.txt

@@ -1,21 +1,11 @@
-   ========================================================================
-   == NOTICE file corresponding to section 4 d of the Apache License,    ==
-   == Version 2.0, in this case for the Spring Integration distribution. ==
-   ========================================================================
+Spring AMQP Framework ${version}
+Copyright (c) 2010-${copyright} Pivotal, Inc.
 
-   This product includes software developed by
-   the Apache Software Foundation (http://www.apache.org).
+This product is licensed to you under the Apache License, Version 2.0
+(the "License"). You may not use this product except in compliance with
+the License.
 
-   The end-user documentation included with a redistribution, if any,
-   must include the following acknowledgement:
-
-     "This product includes software developed by the Spring Framework
-      Project (http://www.spring.io)."
-
-   Alternatively, this acknowledgement may appear in the software itself,
-   if and wherever such third-party acknowledgements normally appear.
-
-   The names "Spring", "Spring Framework", and "Spring AMQP" must
-   not be used to endorse or promote products derived from this software
-   without prior written permission. For written permission, please contact
-   [email protected].
+This product may include a number of subcomponents with separate
+copyright notices and license terms. Your use of the source code for
+these subcomponents is subject to the terms and conditions of the
+subcomponent's license, as noted in the license.txt file.