org.osgi.util.function/pom.xml at main · osgi/org.osgi.util.function · GitHub

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
<?xml version="1.0"?>
<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>
	<groupId>org.osgi</groupId>
	<artifactId>org.osgi.util.function.reactor</artifactId>
	<version>${revision}</version>
	<packaging>pom</packaging>
	<description>OSGi Function Package (Promises Specification)</description>

	<!-- The version lives in exactly one place: .mvn/maven.config
	     (-Drevision=...). Maven picks that file up from the repo root for
	     every build, and the release workflow matches the git tag against
	     it. No revision property here — a second copy would just drift. -->
	<parent>
		<groupId>org.osgi</groupId>
		<artifactId>org.osgi.maven.pom.parent</artifactId>
		<version>0.0.1-SNAPSHOT</version>
	</parent>

	<!-- The SNAPSHOT parent is deployed to Central snapshots, not Maven
	     Central. The repositories declared in the parent cannot help to
	     resolve the parent itself, but repositories declared here in the
	     child are used for parent resolution — without this block a fresh
	     clone cannot build. Remove once the parent is a Central release. -->
	<repositories>
		<repository>
			<id>central-snapshots</id>
			<name>Central Snapshots</name>
			<url>https://central.sonatype.com/repository/maven-snapshots/</url>
			<releases>
				<enabled>false</enabled>
			</releases>
			<snapshots>
				<enabled>true</enabled>
			</snapshots>
		</repository>
	</repositories>
	<!-- Plugin and build-extension dependencies (e.g. the tck-bnd-plugins
	     jar on the bnd-maven-plugin classpath) resolve via
	     pluginRepositories, not repositories — same snapshot store. -->
	<pluginRepositories>
		<pluginRepository>
			<id>central-snapshots</id>
			<name>Central Snapshots</name>
			<url>https://central.sonatype.com/repository/maven-snapshots/</url>
			<releases>
				<enabled>false</enabled>
			</releases>
			<snapshots>
				<enabled>true</enabled>
			</snapshots>
		</pluginRepository>
	</pluginRepositories>

	<properties>
		<osgi.scm.repository>osgi/org.osgi.util.function</osgi.scm.repository>
	</properties>

	<modules>
		<module>api</module>
	</modules>

	<build>
		<plugins>
			<!-- Resolve ${revision} before install/deploy. The parent manages this
			     plugin but does not activate it, so every installed pom kept the
			     unresolved property in its parent reference: consuming a module
			     from the repository — or publishing it — then fails. Declared
			     here in the reactor, the modules inherit it. -->
			<plugin>
				<groupId>org.codehaus.mojo</groupId>
				<artifactId>flatten-maven-plugin</artifactId>
			</plugin>
		</plugins>
	</build>
</project>