Spring/spring-integration
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

INT-1280: ship commons code out to external project

Browse Source
This commit is contained in:
David Syer
2010-08-25 12:22:27 +00:00
parent 78deab7677
commit d98ff8eaa1
24 changed files with 89 additions and 543 deletions
Download Patch File Download Diff File Expand all files Collapse all files

89
spring-integration-parent/pom.xml
View File

@@ -58,6 +58,9 @@
</snapshotRepository>
</distributionManagement>
</profile>
<profile>
<id>legacy-build</id>
</profile>
</profiles>
<distributionManagement>
<!-- see 'staging' profile for dry-run deployment settings -->
@@ -77,12 +80,15 @@
<url>s3://maven.springframework.org/snapshot</url>
</snapshotRepository>
</distributionManagement>
<dependencyManagement><!--
inheritable <dependency> declarations for child poms. children still must
explicitly declare the groupId/artifactId of these dependencies in order
for them to show up on the classpath, but metadata like <version> and
<scope> are inherited, which cuts down on verbosity.
see http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-dep-manage.html -->
<dependencyManagement>
<!--
inheritable <dependency> declarations for child poms. children still
must explicitly declare the groupId/artifactId of these dependencies
in order for them to show up on the classpath, but metadata like
<version> and <scope> are inherited, which cuts down on verbosity.
see
http://www.sonatype.com/books/mvnref-book/reference/pom-relationships-sect-dep-manage.html
-->
<dependencies>
<dependency>
<groupId>org.aspectj</groupId>
@@ -174,11 +180,18 @@
<artifactId>spring-integration-stream</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>org.springframework.commons</groupId>
<artifactId>spring-commons-serializer</artifactId>
<version>1.0.0.BUILD-SNAPSHOT</version>
</dependency>
<!-- test-scoped dependencies -->
<dependency><!--
while cglib is not necessarily a 'test'-related dependency, it
is only used for testing purposes by child modules thus it's
scope has been generalized to 'test' here -->
<dependency>
<!--
while cglib is not necessarily a 'test'-related dependency, it is
only used for testing purposes by child modules thus it's scope has
been generalized to 'test' here
-->
<groupId>cglib</groupId>
<artifactId>cglib-nodep</artifactId>
<version>${cglib.version}</version>
@@ -234,11 +247,14 @@
</dependency>
</dependencies>
</dependencyManagement>
<dependencies><!--
dependency definitions to be inherited by child poms. any <dependency>
declarations here will automatically show up on child project classpaths.
only items that are truly common across all projects (modules and samples)
should go here. otherwise, consider <dependencyManagement> above -->
<dependencies>
<!--
dependency definitions to be inherited by child poms. any
<dependency> declarations here will automatically show up on child
project classpaths. only items that are truly common across all
projects (modules and samples) should go here. otherwise, consider
<dependencyManagement> above
-->
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
@@ -249,7 +265,10 @@
<build>
<extensions>
<extension>
<!-- available only in the springframework maven repository. see <repositories> section below -->
<!--
available only in the springframework maven repository. see
<repositories> section below
-->
<groupId>org.springframework.build.aws</groupId>
<artifactId>org.springframework.build.aws.maven</artifactId>
<version>3.0.0.RELEASE</version>
@@ -332,14 +351,20 @@
</plugins>
<pluginManagement>
<plugins>
<plugin><!--
configures the springsource bundlor plugin, which generates OSGI-compatible MANIFEST.MF
files during the 'compile' phase of the maven build. this plugin is declared within
the pluginManagement section because not every module that inherits from this pom
needs bundlor's services, e.g.: spring-integration-samples and all its children. for this
reason, all modules that wish to use bundlor must declare it explicitly. it is not necessary
to specify the <version> or <configuration> sections, but groupId and artifactId are required.
see http://static.springsource.org/s2-bundlor/1.0.x/user-guide/html/ch04s03.html for more info -->
<plugin>
<!--
configures the springsource bundlor plugin, which generates
OSGI-compatible MANIFEST.MF files during the 'compile' phase of
the maven build. this plugin is declared within the
pluginManagement section because not every module that inherits
from this pom needs bundlor's services, e.g.:
spring-integration-samples and all its children. for this reason,
all modules that wish to use bundlor must declare it explicitly.
it is not necessary to specify the <version> or <configuration>
sections, but groupId and artifactId are required. see
http://static.springsource.org/s2-bundlor/1.0.x/user-guide/html/ch04s03.html
for more info
-->
<groupId>com.springsource.bundlor</groupId>
<artifactId>com.springsource.bundlor.maven</artifactId>
<version>1.0.0.RELEASE</version>
@@ -355,8 +380,11 @@
</execution>
</executions>
</plugin>
<plugin><!--
configures the jar plugin to pick up the manifest created by bundlor (see above) -->
<plugin>
<!--
configures the jar plugin to pick up the manifest created by
bundlor (see above)
-->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<version>2.2</version>
@@ -371,9 +399,12 @@
</build>
<reporting>
<plugins>
<plugin><!--
significantly speeds up the 'Dependencies' report during site creation
see http://old.nabble.com/Skipping-dependency-report-during-Maven2-site-generation-td20116761.html -->
<plugin>
<!--
significantly speeds up the 'Dependencies' report during site
creation see
http://old.nabble.com/Skipping-dependency-report-during-Maven2-site-generation-td20116761.html
-->
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-project-info-reports-plugin</artifactId>
<version>2.1</version>