Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
npm run format
for formatting the code before submitting the pull request.🐛 Bug Fix: Handle spaces in Maven POM file paths on Windows agents
Problem
When running a JFrog Maven task on a Windows agent, if the path to the
pom.xml
file contains spaces (e.g.,C:\agent\_work\My Project\pom.xml
), the CLI fails with the following error:ERROR org.apache.maven.cli.MavenCli - Non-readable POM E:
This occurs because the POM file path is not properly quoted, which causes Maven to misinterpret the argument.
Root Cause
The
pom.xml
file path was passed to the CLI without quotes, resulting in broken CLI commands when the path contains spaces.Fix
Quote the
pom.xml
file path usingutils.quote()
when appending it to the CLI command arguments.Before:
After:
Tests Added
✅ Unit Test: spaces_test.js to verify that POM file paths with spaces are properly quoted.
✅ Integrated Test Suite: Added under tests.ts to ensure regression coverage.