From de8ff28a5aeeb75c1b1d2bba23dabe0b345eee95 Mon Sep 17 00:00:00 2001
From: Volker Diels-Grabsch <v@njh.eu>
Date: Fri, 15 Aug 2025 14:17:02 +0200
Subject: [PATCH] fetchMavenArtifact: fix metadata support

Fix fetchMavenArtifact to forward the "meta" attribute to mkDerivation
rather than fetchurl.

(cherry picked from commit f81a2dfa52e68530368b8eb1580376f49dc2ef2a)
---
 pkgs/build-support/fetchmavenartifact/default.nix | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/pkgs/build-support/fetchmavenartifact/default.nix b/pkgs/build-support/fetchmavenartifact/default.nix
index eca360057a60..1da312f5d100 100644
--- a/pkgs/build-support/fetchmavenartifact/default.nix
+++ b/pkgs/build-support/fetchmavenartifact/default.nix
@@ -31,6 +31,8 @@ args@{
   # and `urls` can be specified, not both.
   url ? "",
   urls ? [ ],
+  # Metadata
+  meta ? { },
   # The rest of the arguments are just forwarded to `fetchurl`.
   ...
 }:
@@ -71,6 +73,7 @@ let
       "classifier"
       "repos"
       "url"
+      "meta"
     ]
     // {
       urls = urls_;
@@ -79,7 +82,7 @@ let
   );
 in
 stdenv.mkDerivation {
-  inherit pname version;
+  inherit pname version meta;
   dontUnpack = true;
   # By moving the jar to $out/share/java we make it discoverable by java
   # packages packages that mention this derivation in their buildInputs.