<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>biz.aQute.bnd-test</groupId>
	<artifactId>test-in-build-pluginManagement-inheritance</artifactId>
	<version>0.0.1</version>
	<packaging>pom</packaging>

	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
		<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
	</properties>

	<modules>
		<module>test-inheriting-api-bundle</module>
	</modules>

	<build>
		<pluginManagement>
			<plugins>
				<plugin>
					<groupId>biz.aQute.bnd</groupId>
					<artifactId>bnd-maven-plugin</artifactId>
					<version>@project.version@</version>
					<executions>
						<execution>
							<id>default-bnd-process</id>
							<goals>
								<goal>bnd-process</goal>
							</goals>
						</execution>
					</executions>
					<configuration>
						<skip>false</skip>
						<bnd><![CDATA[
X-ParentProjectProperty: it failed
X-ParentProjectProperty2: it worked
Bundle-SymbolicName: ${project.groupId}.${project.artifactId}
]]></bnd>
					</configuration>
				</plugin>

				<!-- The following configuration is required because bnd-maven-plugin
					generates the manifest to target/classes/META-INF/MANIFEST.MF but the normal
					maven-jar-plugin does not use it. If the jar-plugin is patched to pick up
					the manifest from this location, then the following config is not needed. -->
				<plugin>
					<groupId>org.apache.maven.plugins</groupId>
					<artifactId>maven-jar-plugin</artifactId>
					<version>3.1.1</version>
					<configuration>
						<archive>
							<manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile>
						</archive>
					</configuration>
				</plugin>
			</plugins>
		</pluginManagement>
	</build>
</project>
