-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathpom.xml
More file actions
119 lines (105 loc) · 3.81 KB
/
Copy pathpom.xml
File metadata and controls
119 lines (105 loc) · 3.81 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
<?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 https://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<!--
Build the starter against Spring Boot 3.5 (minimum supported version).
The library is also compatible with Spring Boot 4.0.x.
-->
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>3.5.16</version>
<relativePath></relativePath>
</parent>
<groupId>com.patbaumgartner.embabel</groupId>
<artifactId>embabel-workflow-visualizer-parent</artifactId>
<version>0.3.0-SNAPSHOT</version>
<packaging>pom</packaging>
<name>embabel-workflow-visualizer-parent</name>
<description>Spring Boot starter that visualizes Embabel agent workflows as an actuator endpoint and interactive UI.</description>
<modules>
<module>embabel-workflow-visualizer-starter</module>
<module>embabel-sample-application</module>
</modules>
<properties>
<java.version>21</java.version>
<jreleaser.version>1.25.0</jreleaser.version>
</properties>
<build>
<plugins>
<!--
Attach sources jar to every module so consumers can navigate to library
source code in their IDE and so that GitHub Packages / Maven Central serve them.
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<executions>
<execution>
<id>attach-sources</id>
<goals>
<goal>jar-no-fork</goal>
</goals>
</execution>
</executions>
</plugin>
<!--
Attach javadoc jar for the same reason.
Javadoc failures are treated as errors during the release lifecycle.
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<doclint>none</doclint>
<source>${java.version}</source>
<release>${java.version}</release>
</configuration>
<executions>
<execution>
<id>attach-javadocs</id>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
<!--
JReleaser Maven plugin — used locally to stage, sign, and publish
releases to Maven Central. In CI the jreleaser/release-action@v2
GitHub Action is used instead, reading jreleaser.yml at the root.
-->
<plugin>
<groupId>org.jreleaser</groupId>
<artifactId>jreleaser-maven-plugin</artifactId>
<version>${jreleaser.version}</version>
<inherited>false</inherited>
</plugin>
</plugins>
</build>
<url>https://github.com/patbaumgartner/embabel-workflow-visualizer</url>
<licenses>
<license>
<name>Apache License, Version 2.0</name>
<url>https://www.apache.org/licenses/LICENSE-2.0</url>
<distribution>repo</distribution>
</license>
</licenses>
<developers>
<developer>
<id>patbaumgartner</id>
<name>Patrick Baumgartner</name>
<url>https://github.com/patbaumgartner</url>
</developer>
</developers>
<scm>
<connection>scm:git:https://github.com/patbaumgartner/embabel-workflow-visualizer.git</connection>
<developerConnection>scm:git:https://github.com/patbaumgartner/embabel-workflow-visualizer.git</developerConnection>
<url>https://github.com/patbaumgartner/embabel-workflow-visualizer</url>
<tag>HEAD</tag>
</scm>
<issueManagement>
<system>GitHub Issues</system>
<url>https://github.com/patbaumgartner/embabel-workflow-visualizer/issues</url>
</issueManagement>
</project>