38e6f4462c
Currently the same pom_fake.xml controls both installing the plugin-api in local Maven repository (typical use case for a contributor) and deploying it on Google bucket (typical use case for a maintainer). To fit the both use cases that file contains stuff needed for uploading to Google bucket only: 'gs-maven-wagon' artifact and the repository to fetch it from. Because the "best" build tool in the world randomly and unreproducible fails to fetch that artifact [1], frustrating the potential contributors, for reasons that nobody knows and understands, separate these use cases from each other, and strip the stuff from pom_fake.xml needed for deployment of plugin-api. The cost is code duplication. The advantage of doing it: buck build api_install just works. Always. [1] https://gist.github.com/mulby/092fee5f5962aafbbb25#file-gerrit-build-error-txt Change-Id: I842335907ef8721f4126bcd90e395f7748aefc74
7 lines
214 B
XML
7 lines
214 B
XML
<project xmlns="http://maven.apache.org/POM/4.0.0">
|
|
<modelVersion>4.0.0</modelVersion>
|
|
<groupId>com.google.gerrit</groupId>
|
|
<artifactId>Gerrit-Code-Review-Maven</artifactId>
|
|
<version>1</version>
|
|
</project>
|