12e5b6d6dSopenharmony_ci<?xml version="1.0" encoding="UTF-8"?>
22e5b6d6dSopenharmony_ci<!-- © 2020 and later: Unicode, Inc. and others.
32e5b6d6dSopenharmony_ci     License & terms of use: http://www.unicode.org/copyright.html
42e5b6d6dSopenharmony_ci     See README.txt for instructions on updating the local repository.
52e5b6d6dSopenharmony_ci     -->
62e5b6d6dSopenharmony_ci<project xmlns="http://maven.apache.org/POM/4.0.0"
72e5b6d6dSopenharmony_ci         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
82e5b6d6dSopenharmony_ci         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
92e5b6d6dSopenharmony_ci    <modelVersion>4.0.0</modelVersion>
102e5b6d6dSopenharmony_ci
112e5b6d6dSopenharmony_ci    <!-- This POM file acts as a parent POM file for any tool which is built
122e5b6d6dSopenharmony_ci         via Maven and requires access to the CLDR data APIs. This POM file
132e5b6d6dSopenharmony_ci         and the other files in this directory encapsulate the somewhat messy
142e5b6d6dSopenharmony_ci         task of including the Ant-built CLDR JAR file in Maven projects. -->
152e5b6d6dSopenharmony_ci
162e5b6d6dSopenharmony_ci    <!-- Declares this to be a POM that's included by other POM files. -->
172e5b6d6dSopenharmony_ci    <packaging>pom</packaging>    
182e5b6d6dSopenharmony_ci    
192e5b6d6dSopenharmony_ci    <!-- This must match any child POM file's <parent> declaration. -->         
202e5b6d6dSopenharmony_ci    <groupId>org.unicode.icu</groupId>
212e5b6d6dSopenharmony_ci    <artifactId>cldr-lib</artifactId>
222e5b6d6dSopenharmony_ci    <version>1.0</version>
232e5b6d6dSopenharmony_ci    
242e5b6d6dSopenharmony_ci    <!-- Important: The "${project.basedir}" property is the directory of the
252e5b6d6dSopenharmony_ci         child POM file, not this directory (and there's no easy way in Maven
262e5b6d6dSopenharmony_ci         to identify the absolute path of a parent POM file). However since
272e5b6d6dSopenharmony_ci         child POM files should have a <parent> declaration with the relative
282e5b6d6dSopenharmony_ci         path in it, we can use that. Note however that this is a bit fragile
292e5b6d6dSopenharmony_ci         and relies on <relativePath> being a directory, not a POM file.
302e5b6d6dSopenharmony_ci         
312e5b6d6dSopenharmony_ci         In order to allow the local repository to work either when it is used
322e5b6d6dSopenharmony_ci         by a child POM file or when it's used directly (e.g. for installing
332e5b6d6dSopenharmony_ci         or purging the cache) when it is invoked from this directory, the
342e5b6d6dSopenharmony_ci           -Dproject.parent.relativePath=""
352e5b6d6dSopenharmony_ci         argument must be given. -->
362e5b6d6dSopenharmony_ci    <repositories>
372e5b6d6dSopenharmony_ci        <repository>
382e5b6d6dSopenharmony_ci            <id>local-maven-repo</id>
392e5b6d6dSopenharmony_ci            <url>file://${project.basedir}/${project.parent.relativePath}</url>
402e5b6d6dSopenharmony_ci        </repository>
412e5b6d6dSopenharmony_ci    </repositories>
422e5b6d6dSopenharmony_ci    
432e5b6d6dSopenharmony_ci    <!-- Ant-built JAR file(s) installed into the local Maven repository in this
442e5b6d6dSopenharmony_ci         directory by the 'install-cldr-jars.sh' script. -->
452e5b6d6dSopenharmony_ci    <dependencies>
462e5b6d6dSopenharmony_ci        <dependency>
472e5b6d6dSopenharmony_ci            <groupId>org.unicode.cldr</groupId>
482e5b6d6dSopenharmony_ci            <artifactId>cldr-api</artifactId>
492e5b6d6dSopenharmony_ci            <version>0.1-SNAPSHOT</version>
502e5b6d6dSopenharmony_ci        </dependency>
512e5b6d6dSopenharmony_ci    </dependencies>
522e5b6d6dSopenharmony_ci</project>
532e5b6d6dSopenharmony_ci
54