[
https://issues.apache.org/jira/browse/TIKA-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048577#comment-18048577
]
ASF GitHub Bot commented on TIKA-4609:
--------------------------------------
nddipiazza commented on PR #2510:
URL: https://github.com/apache/tika/pull/2510#issuecomment-3702450627
## About the Maven Caching Change
Added `cache: 'maven'` to all `setup-java@v4` steps.
**What it does:**
- Caches `~/.m2/repository` between CI runs
- Uses `hashFiles('**/pom.xml')` to invalidate cache when dependencies change
- Built-in feature of setup-java@v4 action
**Benefits:**
- Saves ~30-60 seconds per build by avoiding repeated dependency downloads
- Reduces bandwidth usage
- No code changes required - just one line per workflow
**How it works:**
```yaml
- name: Set up JDK ${{ matrix.java }}
uses: actions/setup-java@v4
with:
distribution: 'temurin'
java-version: ${{ matrix.java }}
cache: 'maven' # ← This enables caching
```
This is equivalent to manually using `actions/cache@v4` but more concise.
See [setup-java caching
docs](https://github.com/actions/setup-java#caching-packages-dependencies).
The cache will be automatically invalidated if any pom.xml files change.
> 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
> # Add Github CI caching as well
> 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)
