[
https://issues.apache.org/jira/browse/TIKA-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18048578#comment-18048578
]
ASF GitHub Bot commented on TIKA-4609:
--------------------------------------
nddipiazza commented on PR #2510:
URL: https://github.com/apache/tika/pull/2510#issuecomment-3702468976
## Transient Maven Central Issue
The current failure is **not related to our changes**. It's a
network/repository connectivity issue:
```
Error: Extension eu.maveniverse.maven.nisse:extension:0.7.0 or one of its
dependencies could not be resolved
Failed to read artifact descriptor for
eu.maveniverse.maven.nisse:extension:jar:0.7.0
```
This is a transient Maven repository issue - the Nisse extension can't be
downloaded from Maven Central. This happens occasionally in CI environments.
**Evidence this is unrelated to our changes:**
- Our changes only affect Maven output flags and caching
- The error occurs during extension resolution, before our flags are even
used
- This is a known transient issue with Maven extensions
**Options:**
1. Wait and re-run the failed jobs (usually resolves itself)
2. Check if main branch has the same issue
3. Temporarily disable the Nisse extension if this persists
I'll monitor the in-progress runs to see if they succeed.
> 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)
