5e9382c23a
This is so they can be updated in a minimal amount of places and leverage the maven hierarchy to propagate them where appropriate. While working with SNAPSHOT releases of Spring Boot, Spring Integration, and Spring Cloud, it required touching every pom.xml file in order to reflect the use of the SNAPSHOT. After this change, it will only be required to change the property in the top functions pom.xml and the versions will reflect to all submodules. Maven introduced the ability use a key property, revision to propagate this information to the <parent> declarations in each pom. This was enabled in Maven 3.5+ https://maven.apache.org/maven-ci-friendly.html
27 lines
775 B
XML
27 lines
775 B
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<project xmlns="http://maven.apache.org/POM/4.0.0"
|
|
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
|
|
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
|
|
<modelVersion>4.0.0</modelVersion>
|
|
|
|
<parent>
|
|
<groupId>org.springframework.cloud.fn</groupId>
|
|
<artifactId>java-functions-function-parent</artifactId>
|
|
<version>${revision}</version>
|
|
</parent>
|
|
|
|
<artifactId>payload-converter-function</artifactId>
|
|
<name>payload-converter-function</name>
|
|
<description>Utility message conversion functions</description>
|
|
|
|
<dependencies>
|
|
|
|
<dependency>
|
|
<groupId>org.springframework</groupId>
|
|
<artifactId>spring-messaging</artifactId>
|
|
</dependency>
|
|
|
|
</dependencies>
|
|
|
|
</project>
|