Check MAVEN_PARAMS for -f flag in metadata fetch

[releng/global-jjb.git] / releasenotes / notes / metadata-pom-path-d67d24874f3e1f43.yaml

diff --git a/releasenotes/notes/metadata-pom-path-d67d24874f3e1f43.yaml b/releasenotes/notes/metadata-pom-path-d67d24874f3e1f43.yaml
new file mode 100644 (file)
index 0000000..04ebaed
--- /dev/null
+++ b/releasenotes/notes/metadata-pom-path-d67d24874f3e1f43.yaml
@@ -0,0 +1,7 @@
+---
+fixes:
+  - |
+    maven-fetch-metadata.sh was not respecting the "-f" (for file path)
+    flag in MAVEN_PARAMS, causing lf-maven-merge jobs that utilize this
+    flag to fail. It will now set a path based on this flag if it is present,
+    or default to the current working directory.