[
https://issues.apache.org/jira/browse/TIKA-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048574#comment-18048574
]
ASF GitHub Bot commented on TIKA-4609:
--------------------------------------
nddipiazza commented on PR #2510:
URL: https://github.com/apache/tika/pull/2510#issuecomment-3702441564
Updated the PR to fix the Windows parsing issue and add Maven caching:
## Changes in Latest Commit
### 1. Fixed Windows Command Parsing
**Problem:** Windows PowerShell/CMD was treating the space before `-D` as an
argument separator, causing this error:
```
[ERROR] Unknown lifecycle phase
".slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn"
```
**Solution:** Quote the property definition:
```bash
# Before (broken on Windows)
-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn
# After (works on all platforms)
"-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn"
```
### 2. Added Maven Dependency Caching
Added `cache: 'maven'` to all `setup-java@v4` steps to:
- Cache `~/.m2/repository` between builds
- Significantly speed up builds by avoiding repeated downloads
- Reduce bandwidth usage
## What This Achieves
✅ Reduced CI log verbosity (Maven transfer messages suppressed)
✅ Works on Windows, Linux, and all platforms
✅ Faster builds with dependency caching
✅ Error messages are now easily visible in logs
Previous failure: https://github.com/apache/tika/actions/runs/20618695661
> Reduce Maven verbosity in GitHub Actions workflows
> --------------------------------------------------
>
> Key: TIKA-4609
> URL: https://issues.apache.org/jira/browse/TIKA-4609
> Project: Tika
> Issue Type: Improvement
> Reporter: Nicholas DiPiazza
> Assignee: Nicholas DiPiazza
> Priority: Minor
>
> h2. Problem
> The GitHub Actions workflows are running Maven with extremely verbose output,
> making it nearly impossible to read error messages in the GitHub Actions UI.
> The log output is so verbose that users have to download the raw log files to
> find actual error messages.
> h2. Impact
> * Developers cannot quickly diagnose CI failures
> * CI logs are difficult to navigate and scroll through
> * Error messages are buried in verbose Maven transfer progress output
> * This wastes developer time troubleshooting CI issues
> h2. Solution
> Reduce Maven verbosity in GitHub Actions workflows by:
> # Using {{-B}} (batch mode) to reduce progress output
> # Using
> {{-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn}}
> to suppress download progress
> # Ensuring error messages are easily visible in the CI output
> h2. Affected Files
> * {{.github/workflows/*.yml}} - All workflow files that run Maven commands
> h2. Example
> *Current:* {{mvn clean test install javadoc:aggregate -Pci}}
> *Proposed:* {{mvn clean test install javadoc:aggregate -Pci -B
> -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
