[ 
https://issues.apache.org/jira/browse/TIKA-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048572#comment-18048572
 ] 

ASF GitHub Bot commented on TIKA-4609:
--------------------------------------

nddipiazza opened a new pull request, #2510:
URL: https://github.com/apache/tika/pull/2510

   ## Summary
   Fixes https://issues.apache.org/jira/browse/TIKA-4609
   
   The original commit 218508d48 accidentally introduced line breaks in the 
Maven property name, breaking Windows builds.
   
   ## Problem
   The property name was split across lines with a space:
   ```
   -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfe 
r.Slf4jMavenTransferListener=warn
   ```
   
   This caused Maven to not recognize the property correctly.
   
   ## Solution
   Keep the full property name on one line without spaces:
   ```
   
-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn
   ```
   
   ## Changes
   - Fix all 5 workflow files (.github/workflows/*.yml)
   - Properly suppress Maven transfer listener output
   - Maintains the original goal of reducing CI log verbosity
   
   ## Testing
   This should make CI logs cleaner by:
   - Using `-B` (batch mode) to suppress interactive progress
   - Suppressing Maven download/upload progress messages
   - Making error messages more visible
   
   Without breaking Windows or any other builds.




> 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)

Reply via email to