Please reconsider effectively simply ignoring this issue
I really doubt anyone is actively ignoring this issue. If you're referring to me reducing priority, please note that before I reviewed most of the unresolved core issues in this tracker, we had dozens and dozens of blocker/critical core issues (in many cases, just like this one, they weren't actually that severe), and nobody cared about those either. It's not like an alarm goes off somewhere whenever an issue with high "priority" gets filed.
As far as I can tell, priority is given to regressions, issues affecting many users, and issues that the developers themselves want to see fixed (and, in the case of Cloudbees employed Jenkins devs, issues from customer support requests). This issue seems to be none of the above.
Please make sure this issue occurs on latest weekly or LTS release of Jenkins and latest available Maven Plugin. Update the issue with that information once you do.
Reducing priority as this is clearly neither Blocker nor Critical, and since it seems to be rather unusual (it doesn't look like many actually need this) I wouldn't consider it Major loss of functionality either.