|
| 1 | +<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
| 2 | + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> |
| 3 | + <modelVersion>4.0.0</modelVersion> |
| 4 | + <groupId>org.apache.hadoop.fs.glusterfs</groupId> |
| 5 | + <artifactId>glusterfs</artifactId> |
| 6 | + <packaging>jar</packaging> |
| 7 | + <version>2.0-SNAPSHOT</version> |
| 8 | + <name>glusterfs</name> |
| 9 | + <url>http://maven.apache.org</url> |
| 10 | + <dependencies> |
| 11 | + <dependency> |
| 12 | + <groupId>junit</groupId> |
| 13 | + <artifactId>junit</artifactId> |
| 14 | + <version>4.11</version> |
| 15 | + </dependency> |
| 16 | + <dependency> |
| 17 | + <groupId>org.apache.hadoop</groupId> |
| 18 | + <artifactId>hadoop-core</artifactId> |
| 19 | + <version>1.2.1</version> |
| 20 | + </dependency> |
| 21 | + <dependency> |
| 22 | + <groupId>org.apache.hadoop</groupId> |
| 23 | + <artifactId>hadoop-test</artifactId> |
| 24 | + <version>1.2.1</version> |
| 25 | + <scope>test</scope> |
| 26 | + </dependency> |
| 27 | + <dependency> |
| 28 | + <groupId>org.apache.hadoop</groupId> |
| 29 | + <artifactId>hadoop-test</artifactId> |
| 30 | + <version>1.2.1</version> |
| 31 | + <scope>test</scope> |
| 32 | + </dependency> |
| 33 | + <dependency> |
| 34 | + <groupId>org.slf4j</groupId> |
| 35 | + <artifactId>slf4j-api</artifactId> |
| 36 | + <version>1.5.8</version> |
| 37 | + <scope>compile</scope> |
| 38 | + </dependency> |
| 39 | + <dependency> |
| 40 | + <groupId>org.slf4j</groupId> |
| 41 | + <artifactId>slf4j-log4j12</artifactId> |
| 42 | + <version>1.7.3</version> |
| 43 | + </dependency> |
| 44 | + </dependencies> |
| 45 | + <build> |
| 46 | + <plugins> |
| 47 | + <plugin> |
| 48 | + <groupId>org.apache.maven.plugins</groupId> |
| 49 | + <artifactId>maven-surefire-plugin</artifactId> |
| 50 | + <version>2.14</version> |
| 51 | + <configuration> |
| 52 | + <!-- |
| 53 | + run "export GLUSTER_MOUNT=/mnt/glusterfs |
| 54 | + export HCFS_FILE_SYSTEM_CONNECTOR=org.gluster.test.GlusterFileSystemTestConnector |
| 55 | + export HCFS_CLASSNAME=org.apache.hadoop.fs.glusterfs.GlusterFileSystem" |
| 56 | + --> |
| 57 | + <systemProperties> |
| 58 | + <property> |
| 59 | + <name>GLUSTER_MOUNT</name> |
| 60 | + <value>${GLUSTER_MOUNT}</value> |
| 61 | + </property> |
| 62 | + <property> |
| 63 | + <name>HCFS_CLASSNAME</name> |
| 64 | + <value>${HCFS_CLASSNAME}</value> |
| 65 | + </property> |
| 66 | + <property> |
| 67 | + <name>HCFS_FILE_SYSTEM_CONNECTOR</name> |
| 68 | + <value>${HCFS_FILE_SYSTEM_CONNECTOR}</value> |
| 69 | + </property> |
| 70 | + |
| 71 | + </systemProperties> |
| 72 | + </configuration> |
| 73 | + </plugin> |
| 74 | + |
| 75 | + <plugin> |
| 76 | + <groupId>org.apache.maven.plugins</groupId> |
| 77 | + <artifactId>maven-compiler-plugin</artifactId> |
| 78 | + <version>2.3.2</version> |
| 79 | + <configuration> |
| 80 | + <source>1.5</source> |
| 81 | + <target>1.5</target> |
| 82 | + </configuration> |
| 83 | + </plugin> |
| 84 | + |
| 85 | +<plugin> |
| 86 | + <groupId>pl.project13.maven</groupId> |
| 87 | + <artifactId>git-commit-id-plugin</artifactId> |
| 88 | + <version>2.1.4</version> |
| 89 | + <executions> |
| 90 | + <execution> |
| 91 | + <goals> |
| 92 | + <goal>revision</goal> |
| 93 | + </goals> |
| 94 | + </execution> |
| 95 | + </executions> |
| 96 | + |
| 97 | + <configuration> |
| 98 | + <!-- that's the default value, you don't have to set it --> |
| 99 | + <prefix>git</prefix> |
| 100 | + |
| 101 | + <!-- that's the default value --> |
| 102 | + <dateFormat>dd.MM.yyyy '@' HH:mm:ss z</dateFormat> |
| 103 | + |
| 104 | + <!-- true is default here, it prints some more information during the build --> |
| 105 | + <verbose>true</verbose> |
| 106 | + |
| 107 | + <!-- |
| 108 | + If you'd like to tell the plugin where your .git directory is, |
| 109 | + use this setting, otherwise we'll perform a search trying to |
| 110 | + figure out the right directory. It's better to add it explicite IMHO. |
| 111 | + --> |
| 112 | + <dotGitDirectory>${project.basedir}/.git</dotGitDirectory> |
| 113 | + |
| 114 | + <!-- ALTERNATE SETUP - GENERATE FILE --> |
| 115 | + <!-- |
| 116 | + If you want to keep git information, even in your WAR file etc, |
| 117 | + use this mode, which will generate a properties file (with filled out values) |
| 118 | + which you can then normally read using new Properties().load(/**/) |
| 119 | + --> |
| 120 | + |
| 121 | + <!-- |
| 122 | + this is true by default; You may want to set this to false, if the plugin should run inside a |
| 123 | + <packaging>pom</packaging> project. Most projects won't need to override this property. |
| 124 | + |
| 125 | + For an use-case for this kind of behaviour see: https://github.com/ktoso/maven-git-commit-id-plugin/issues/21 |
| 126 | + --> |
| 127 | + <skipPoms>true</skipPoms> |
| 128 | + |
| 129 | + <!-- this is false by default, forces the plugin to generate the git.properties file --> |
| 130 | + <generateGitPropertiesFile>true</generateGitPropertiesFile> |
| 131 | + |
| 132 | + <!-- The path for the to be generated properties file, it's relative to ${project.basedir} --> |
| 133 | + <generateGitPropertiesFilename>src/main/resources/git.properties</generateGitPropertiesFilename> |
| 134 | + |
| 135 | + <!-- true by default, controls whether the plugin will fail when no .git directory is found, when set to false the plugin will just skip execution --> |
| 136 | + <!-- @since 2.0.4 --> |
| 137 | + <failOnNoGitDirectory>false</failOnNoGitDirectory> |
| 138 | + |
| 139 | + <!-- @since 2.1.0 --> |
| 140 | + <!-- |
| 141 | + read up about git-describe on the in man, or it's homepage - it's a really powerful versioning helper |
| 142 | + and the recommended way to use git-commit-id-plugin. The configuration bellow is optional, |
| 143 | + by default describe will run "just like git-describe on the command line", even though it's a JGit reimplementation. |
| 144 | + --> |
| 145 | + <gitDescribe> |
| 146 | + <!-- This will show the available tags--> |
| 147 | + <tags>true</tags> |
| 148 | + |
| 149 | + <!-- don't generate the describe property --> |
| 150 | + <skip>false</skip> |
| 151 | + <!-- |
| 152 | + if no tag was found "near" this commit, just print the commit's id instead, |
| 153 | + helpful when you always expect this field to be not-empty |
| 154 | + --> |
| 155 | + <always>false</always> |
| 156 | + <!-- |
| 157 | + how many chars should be displayed as the commit object id? |
| 158 | + 7 is git's default, |
| 159 | + 0 has a special meaning (see end of this README.md), |
| 160 | + and 40 is the maximum value here |
| 161 | + --> |
| 162 | + <abbrev>7</abbrev> |
| 163 | + |
| 164 | + <!-- when the build is triggered while the repo is in "dirty state", append this suffix --> |
| 165 | + <dirty>-dirty</dirty> |
| 166 | + |
| 167 | + <!-- |
| 168 | + always print using the "tag-commits_from_tag-g_commit_id-maybe_dirty" format, even if "on" a tag. |
| 169 | + The distance will always be 0 if you're "on" the tag. |
| 170 | + --> |
| 171 | + <forceLongFormat>false</forceLongFormat> |
| 172 | + </gitDescribe> |
| 173 | + </configuration> |
| 174 | + |
| 175 | + </plugin> |
| 176 | + |
| 177 | + </plugins> |
| 178 | + </build> |
| 179 | +</project> |
0 commit comments