PREQ-7452 Maven build: normalize Windows backslash paths when pushing artifacts

[mary-georgiou]

Updated the paths to count also for windows path seperators.

---

Summary by Gitar

• Build improvements:
  • Normalized Windows-style backslash paths in build-maven/build.sh to ensure consistent artifact path formatting.
  • Updated grep and sed patterns to handle both / and \ separators for local repository paths.
• Dependency management:
  • Fixed jf config edit in build-maven/deploy-artifacts.sh by adding the --url parameter to prevent field clearing issues.
• Testing:
  • Added regression tests in spec/build-maven_spec.sh to verify path normalization with Windows-style Installing log entries.
  • Updated spec/build-maven_deploy-artifacts_spec.sh to reflect the updated jf config edit command.

_{This will update automatically on new commits.}

[hashicorp-vault-sonar-prod]

PREQ-7452

[Copilot]

Pull request overview

This PR improves cross-platform behavior of the build-maven GitHub Action by ensuring artifact paths extracted from Maven “Installing …” log lines are normalized on Windows runners, so downstream deploy/attestation logic continues to work consistently.

Changes:

• Normalize Windows backslash (\) separators to forward slashes (/) when extracting installed artifact paths from Maven output.
• Update the local-repo prefix stripping logic to support both / and \ separators.
• Add a regression test covering Windows-style Installing ... to C:\...\ .m2\repository\... log entries.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
build-maven/build.sh	Normalizes .m2/repository prefix stripping for both slash styles and converts remaining \ to / for consistent artifact path matching.
spec/build-maven_spec.sh	Adds a regression test verifying that Windows-style Maven “Installing” paths are normalized and emitted correctly.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gitar-bot]

Code Review ✅ Approved 1 resolved / 1 findings

Normalizes Windows backslash paths in Maven build artifacts and updates JFrog CLI integration, resolving the local configuration leak issue.

✅ 1 resolved

✅ Quality: mise.local.toml copied to consumer workspace may clobber/leak config

📄 build-maven/action.yml:211-223
The setup step does cp "$ACTION_PATH_BUILD_MAVEN/mise.local.toml" mise.local.toml into the workspace root and never removes it, so a consuming repo that already has its own mise.local.toml would be overwritten, and an untracked file is left in the working tree afterward (can affect later git/dirty-tree checks). Additionally, jdx/mise-action installs every tool declared in any mise config found at that location, so a pre-existing consumer mise.toml could cause unexpected tool installs/PATH changes. Consider writing the config to a dedicated/temp location (e.g. runner.temp) and pointing mise-action at it, or cleaning up the file after the upload step.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}