Hi Ashish,
for this reason and to be more independent from the availablity of
external server ressources, we are maintaining our own Nexus Repository
at ecomify.
It acts as a cache: if a ressource is not available in our repository,
it pulls them from configured external repositories like maven central
and stores them in our repository. The next request will then be served
from our repository directly.
Not sure if we should maintain an OFBiz repository or if there is a
solution served by infra, maybe ASF wide. I have found
https://repository.apache.org .
Best regards,
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 10.11.26 um 10:29 schrieb Ashish Vijaywargiya via dev:
Hello OFBiz Dev Team,
Very recently I started getting the following error while setting
up/building up the ofbiz project on trunk and release branch 24.09 branch.
Please refer following error details:
Task :buildSrc:extractPluginRequests UP-TO-DATE
> Task :buildSrc:generatePluginAdapters UP-TO-DATE
> Task :buildSrc:compileJava UP-TO-DATE
> Task :buildSrc:compileGroovy
NO-SOURCE
> Task :buildSrc:compileGroovyPlugins UP-TO-DATE
> Task :buildSrc:pluginDescriptors
UP-TO-DATE
> Task :buildSrc:processResources UP-TO-DATE
> Task :buildSrc:classes UP-TO-DATE
> Task :buildSrc:jar UP-TO-DATE
[Incubating] Problems report is available at:
file:///Users/ashish/ofbiz-dev/ofbiz-trunk/build/reports/problems/problems-report.html
FAILURE: Build completed with 2 failures.
1: Task failed with an
exception.
----------
* Where:
Build file '/Users/ashish/ofbiz-dev/ofbiz-trunk/build.gradle' line:
1587 --
* What went wrong:
A problem occurred evaluating root project 'ofbiz'.
> Could not resolve all files for configuration ':runtimeClasspath'.
> Could not resolve com.google.guava:guava:33.8.0-jre.
Required by:
root project 'ofbiz'
> Could not resolve com.google.guava:guava:33.8.0-jre.
> Could not get resource '
https://repo.maven.apache.org/maven2/com/google/guava/guava/33.8.0-jre/guava-33.8.0-jre.pom'.
> Could not GET '
https://repo.maven.apache.org/maven2/com/google/guava/guava/33.8.0-jre/guava-33.8.0-jre.pom'.
> Received status code 429 from server: Too Many
Requests
> Could not resolve
com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer:20261031.1.
Required by:
root project 'ofbiz'
> Could not resolve
com.googlecode.owasp-java-html-sanitizer:owasp-java-html-sanitizer:20261031.1.
> Could not get resource '
https://repo.maven.apache.org/maven2/com/googlecode/owasp-java-html-sanitizer/owasp-java-html-san
itizer/20261031.1/owasp-java-html-sanitizer-20261031.1.pom'.
> Could not GET '
https://repo.maven.apache.org/maven2/com/googlecode/owasp-java-html-sanitizer/owasp-java-html-sanitizer
/20261031.1/owasp-java-html-sanitizer-20261031.1.pom'.
> Received status code 429 from server: Too Many
Requests
> Could not resolve
com.googlecode.libphonenumber:libphonenumber:9.0.43.
Required by:
root project 'ofbiz'
> Could not resolve
com.googlecode.libphonenumber:libphonenumber:9.0.43.
⎿ (timeout 5m)
I get this error while building the project, and when I push any code
changes in my forked version of the project(
https://github.com/ashishvijaywargiya/ofbiz-framework). While pushing a
branch in my fork it compiles and builds the project and sometimes it gives
429 error.
I contacted the SonaType(https://www.sonatype.com/) team who is managing
Maven Repositories. They shared the below link:
https://central.sonatype.org/faq/429-error/
The following snippet is important to consider.
==========================
Maven Central is beginning to enforce consumption limits for unusually
high-volume traffic. If you are seeing a 429 Too Many Requests response,
your organization, network, tool, build environment, or infrastructure
provider may be generating enough aggregate traffic to fall into one of the
highest-consumption groups.
We are introducing these limits gradually. Today, enforcement is focused
only on the highest-volume consumers — the top few percent of traffic
patterns we see across Maven Central. Over time, those thresholds will move
downward as we continue the transition toward a more sustainable
consumption model.
==========================
The Sonatype team suggested the following two options, which I have been
using over the last few days whenever I encounter a **429 Too Many
Requests** error:
1. Setting up a Nexus Repository*
Set up a Nexus repository to manage and host the dependent libraries/JAR
files. This way, whenever the project build process runs, the required JAR
files can be downloaded from our Nexus repository instead of being fetched
directly from Maven Central.
https://www.sonatype.com/products/nexus-community-edition-download
2. Changing the Static IP Address
The alternative option is to change the static IP address from which
requests are sent to the Maven Central server.
I am sharing this email so that we can work together to find a long-term
solution that prevents other users from encountering similar issues while
setting up or building an Apache OFBiz project on their laptops or servers.
I believe other users may also be experiencing the same issue, so it would
be beneficial to explore a common solution that addresses this problem for
the entire Apache OFBiz community.
--
Thank you,
Ashish Vijaywargiya
