integration-tests should not be included in the packaged distribution [SPR-6183]

[spring-projects-issues]

Sam Brannen opened SPR-6183 and commented

The following are currently included in the packaged distribution:

• dist/org.springframework.integration-tests-3.0.0.RC1.jar
• src/org.springframework.integration-tests-sources-3.0.0.RC1.jar

The build should be modified to omit these from the packaged distribution.

---

Affects: 3.0 RC1

Referenced from: commits 523dba7

[spring-projects-issues]

Juergen Hoeller commented

Good point. Arjen, could you please have a look at this and follow up with Ben if necessary?

Juergen

[spring-projects-issues]

nebhale commented

Well, I went to attach two patches to this issue, but it appears that JIRA 4 still has some bugs in it....

The first patch removes the two JARs from the package build:

Index: org.springframework.integration-tests/build.xml
===================================================================
--- org.springframework.integration-tests/build.xml	(revision 2105)
+++ org.springframework.integration-tests/build.xml	(working copy)
@@ -1,6 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <project name="org.springframework.integration-tests">
 	<property file="${basedir}/../build.properties"/>
-	<import file="${basedir}/../build-spring-framework/package-bundle.xml"/>
 	<import file="${basedir}/../spring-build/standard/default.xml"/>
 </project>

The second patch prevents integration test artifacts from being published to the EBR:

Index: org.springframework.integration-tests/build.xml
===================================================================
--- org.springframework.integration-tests/build.xml	(revision 2105)
+++ org.springframework.integration-tests/build.xml	(working copy)
@@ -3,4 +3,7 @@
 	<property file="${basedir}/../build.properties"/>
 	<import file="${basedir}/../build-spring-framework/package-bundle.xml"/>
 	<import file="${basedir}/../spring-build/standard/default.xml"/>
+
+	<target name="publish" description="Publishes all artifacts to remote repositories"/>
+
 </project>

The second patch doesn't do anything with respect to your maven central POMs so someone will need to look that over as well if you choose to apply the second patch.