gnodet opened a new issue, #2752:
URL: https://github.com/apache/uniffle/issues/2752

   ## Description
   
   Building Apache Uniffle with Maven 4.x fails because the project depends on 
`org.apache.apache.resources:apache-incubator-disclaimer-resource-bundle:1.2-SNAPSHOT`,
 which is not available in release repositories.
   
   ## Error
   
   ```
   [ERROR] Failed to execute goal
     org.apache.maven.plugins:maven-remote-resources-plugin:3.0.0:process
     (process-resource-bundles) on project uniffle-parent:
     Error processing remote resources:
     Failed to read artifact descriptor for
     
org.apache.apache.resources:apache-incubator-disclaimer-resource-bundle:jar:1.2-SNAPSHOT:
     The following artifacts could not be resolved:
     
org.apache.apache.resources:apache-incubator-disclaimer-resource-bundle:pom:1.2-SNAPSHOT
 (absent)
   ```
   
   ## Context
   
   This was found during [Maven 4 compatibility testing of Apache 
projects](https://github.com/gnodet/maven4-testing/issues/20523). The Maven 3.x 
build succeeded because it handled the missing SNAPSHOT differently (likely the 
resource bundle was optional or skipped).
   
   Maven 4 enforces stricter artifact resolution. Since the project has 
graduated from the incubator, the incubator disclaimer resource bundle 
reference can likely be removed.
   
   ## Suggested fix
   
   Remove the reference to `apache-incubator-disclaimer-resource-bundle` from 
the `maven-remote-resources-plugin` configuration, since the project has 
graduated from the Apache Incubator.
   
   _Claude Code on behalf of Guillaume Nodet_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to