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

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

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

   ## Problem
   
   The `tika-translate` module fails to build due to 
`jakarta.websocket:jakarta.websocket-api:jar:2.3.0-M1` having a parent POM 
dependency on `org.eclipse.ee4j:project:pom:2.0.0-SNAPSHOT` which is no longer 
available in Maven Central.
   
   **Error:**
   ```
   Failed to execute goal on project tika-translate: Could not collect 
dependencies
   Failed to read artifact descriptor for 
jakarta.websocket:jakarta.websocket-api:jar:2.3.0-M1
   Caused by: Could not find artifact 
org.eclipse.ee4j:project:pom:2.0.0-SNAPSHOT in central-portal-snapshots
   ```
   
   **Failing Build:** 
https://github.com/apache/tika/actions/runs/20508644652/job/58961867443
   
   ## Solution
   
   Downgrade `jakarta.websocket-api` from `2.3.0-M1` (milestone) to `2.2.0` 
(stable release).
   
   **Version comparison:**
   - `2.3.0-M1` parent: `org.eclipse.ee4j:project:pom:2.0.0-SNAPSHOT` ❌ (not 
available)
   - `2.2.0` parent: `org.eclipse.ee4j:project:pom:1.0.9` ✅ (stable, available)
   
   ## Testing
   
   - ✅ `mvn clean compile` succeeds
   - ✅ `mvn test` passes (20 tests, 9 skipped for external services)
   - ✅ No API compatibility issues (2.2.0 is a stable Jakarta EE 11 release)
   
   ## Changes
   
   - `tika-translate/pom.xml`: Changed jakarta.websocket-api version from 
2.3.0-M1 to 2.2.0
   
   Fixes: TIKA-4588




> tika-translate build fails due to jakarta.websocket-api SNAPSHOT parent 
> dependency
> ----------------------------------------------------------------------------------
>
>                 Key: TIKA-4588
>                 URL: https://issues.apache.org/jira/browse/TIKA-4588
>             Project: Tika
>          Issue Type: Bug
>            Reporter: Nicholas DiPiazza
>            Priority: Major
>              Labels: build, dependencies
>
> The tika-translate module fails to build due to a dependency resolution issue 
> with jakarta.websocket-api pulling in a SNAPSHOT dependency that is not 
> available.
> *Error:*
> {code}
> Failed to execute goal on project tika-translate: Could not collect 
> dependencies for project org.apache.tika:tika-translate:bundle:4.0.0-SNAPSHOT
> Failed to read artifact descriptor for 
> jakarta.websocket:jakarta.websocket-api:jar:2.3.0-M1
> Caused by: The following artifacts could not be resolved: 
> org.eclipse.ee4j:project:pom:2.0.0-SNAPSHOT (absent): Could not find artifact 
> org.eclipse.ee4j:project:pom:2.0.0-SNAPSHOT in central-portal-snapshots 
> (https://central.sonatype.com/repository/maven-snapshots/)
> {code}
> *Failing Build:*
> https://github.com/apache/tika/actions/runs/20508644652/job/58961867443#step:4:70408
> *Root Cause:*
> The {{jakarta.websocket:jakarta.websocket-api:jar:2.3.0-M1}} artifact has a 
> parent POM dependency on {{org.eclipse.ee4j:project:pom:2.0.0-SNAPSHOT}} 
> which is a SNAPSHOT version that is no longer available in Maven Central 
> snapshots repository.
> *Impact:*
> - Breaks CI builds intermittently
> - Affects tika-translate module and all downstream modules
> - Prevents successful Maven builds when the SNAPSHOT is unavailable
> *Proposed Solution:*
> 1. Check if jakarta.websocket-api has a newer stable version that doesn't 
> depend on SNAPSHOT parents
> 2. Exclude the problematic transitive dependency if not directly needed
> 3. Pin to a specific version that has stable parent POMs
> 4. Consider using dependency management to override the parent POM version
> *Environment:*
> - Maven build
> - Java 17
> - Affected module: tika-translate



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to