You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Nicholas DiPiazza (Jira)" <ji...@apache.org> on 2025/12/31 15:48:00 UTC
[jira] [Reopened] (TIKA-4609) Reduce Maven verbosity in GitHub Actions workflows
[ https://issues.apache.org/jira/browse/TIKA-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicholas DiPiazza reopened TIKA-4609:
-------------------------------------
Assignee: Nicholas DiPiazza
> 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)