-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathDOWNSTREAM_USAGE_EXAMPLE.xml
More file actions
168 lines (149 loc) · 5.76 KB
/
Copy pathDOWNSTREAM_USAGE_EXAMPLE.xml
File metadata and controls
168 lines (149 loc) · 5.76 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
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
<?xml version="1.0" encoding="UTF-8"?>
<!--
Example: How to use FlossWare Platform BOM in a downstream project
This example shows a project that depends on FlossWare Platform modules
and uses the BOM for centralized dependency management.
Location: In your external project's pom.xml
Group ID: com.example
Artifact ID: my-app
File: pom.xml
-->
<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>
<groupId>com.example</groupId>
<artifactId>my-app</artifactId>
<version>1.0.0</version>
<packaging>jar</packaging>
<name>My Application</name>
<description>Example application using FlossWare Platform</description>
<!-- ========================================== -->
<!-- Dependency Management (BOM Import) -->
<!-- ========================================== -->
<dependencyManagement>
<dependencies>
<!-- Import FlossWare Platform BOM for version management -->
<dependency>
<groupId>org.flossware.jplatform</groupId>
<artifactId>platform-bom</artifactId>
<version>1.1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<!-- ========================================== -->
<!-- Dependencies (Versions inherited from BOM) -->
<!-- ========================================== -->
<dependencies>
<!-- FlossWare Platform Modules -->
<!-- NOTE: No <version> tags needed - inherited from BOM! -->
<!-- Core Platform -->
<dependency>
<groupId>org.flossware.jplatform</groupId>
<artifactId>platform-api</artifactId>
</dependency>
<dependency>
<groupId>org.flossware.jplatform</groupId>
<artifactId>platform-core</artifactId>
</dependency>
<dependency>
<groupId>org.flossware.jplatform</groupId>
<artifactId>platform-messaging</artifactId>
</dependency>
<!-- Management and Monitoring -->
<dependency>
<groupId>org.flossware.jplatform</groupId>
<artifactId>platform-rest-api</artifactId>
</dependency>
<dependency>
<groupId>org.flossware.jplatform</groupId>
<artifactId>platform-metrics-prometheus</artifactId>
</dependency>
<!-- External Dependencies (Versions also inherited from BOM) -->
<!-- Logging -->
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
</dependency>
<dependency>
<groupId>ch.qos.logback</groupId>
<artifactId>logback-classic</artifactId>
</dependency>
<!-- JSON Processing -->
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-databind</artifactId>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.dataformat</groupId>
<artifactId>jackson-dataformat-yaml</artifactId>
</dependency>
<!-- Testing -->
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-core</artifactId>
<scope>test</scope>
</dependency>
</dependencies>
<!-- ========================================== -->
<!-- Build Configuration -->
<!-- ========================================== -->
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.11.0</version>
<configuration>
<release>21</release>
</configuration>
</plugin>
<!-- Verify dependency consistency with BOM -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>3.3.0</version>
<executions>
<execution>
<id>enforce-bom-consistency</id>
<phase>validate</phase>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<!-- Fail if dependencies conflict with BOM -->
<requireReleaseDeps/>
<requirePluginVersions/>
</rules>
</configuration>
</execution>
</executions>
</plugin>
<!-- View effective POM with BOM applied -->
<!-- Command: mvn help:effective-pom -->
<!-- This shows all resolved versions from BOM -->
</plugins>
</build>
<!-- ========================================== -->
<!-- Helpful Commands -->
<!-- ========================================== -->
<!--
View all versions resolved from the BOM:
$ mvn help:effective-pom
View dependency tree with versions:
$ mvn dependency:tree
Check for dependency conflicts:
$ mvn dependency:analyze
View what the BOM provides:
$ mvn dependency:tree -Dartifact=org.flossware.jplatform:platform-bom:1.1:pom
-->
</project>