apache / apache/uniffle

Maven 4 compatibility: build fails due to SNAPSHOT dependency on apache-incubator-disclaimer-resource-bundle

Open Beginner friendly
#2,752 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
454
Forks
172
Avg merge
5d 17h
Merged PRs (30d)
5

Description

## 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_

Contributor guide

Open the contributing guide

Research direction

Start in the project POM at the maven-remote-resources-plugin configuration and locate the apache-incubator-disclaimer-resource-bundle reference. Remove that reference as described, then run the Maven 4 build to confirm the resource-processing failure is resolved and the project still builds successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.