Michael Vorburger created MSHARED-1476:
------------------------------------------
Summary: Maven 4.0.0-rc-3 fails with HTTP 500 when downloading
from JitPack (but Maven 3.9.10 is fine, and it's fully reproducible, and not a
transient server error)
Key: MSHARED-1476
URL: https://issues.apache.org/jira/browse/MSHARED-1476
Project: Maven Shared Components
Issue Type: Bug
Reporter: Michael Vorburger
[~cstamas] this is to follow-up re. our discussion about this [over
here|https://github.com/google/adk-java/issues/173#issuecomment-2952171940]:
Please note that I'm filing this in MSHARED just because I somehow don't seem
to have permission to file issue in MNG on this issues.apache.org/jira - do
you know how to ask to get that fixed? I expect that you'll want to move this
issue to the right project, and set the _Component_ and _Affects Version_
appropriately.
So here is the reproducer:
{{$ git clone [https://github.com/enola-dev/LearningADK.git]}}
{{$ cd LangChain4j}}
{{$ git checkout 077dfc6}}
{{$ ../mvnw clean compile}}
This works great, as it should! But the following fails, and it's fully
reproducible, and not a transient server error, and the only difference is
[https://github.com/enola-dev/LearningADK/commit/077dfc6a83ea04841c37d566339c69f5cb2bfa61:]
{{$ git checkout 0578de9}}
{{$ rm -rf ~/.m2/repository/com/github/enola-dev}}
{{$ ../mvnw clean compile}}
{{[INFO] Scanning for projects...}}
{{[INFO]}}
{{[INFO] ---------------------------------------------{-}<
dev.enola.adk:langchain4j >{-}----------------------------------------------}}
{{[INFO] Building langchain4j 0.0.1-SNAPSHOT}}
{{[INFO] from pom.xml}}
{{[INFO] --------------------------------------------------------{-}[ jar
]{-}---------------------------------------------------------}}
{{[WARNING] Version not locked for default bindings plugins
[maven-clean-plugin, maven-resources-plugin, maven-compiler-plugin], you should
define versions in pluginManagement section of your pom.xml or parent}}
{{Downloading from jitpack.io:
[https://jitpack.io/com/github/enola-dev/adk-java/google-adk-langchain4j/LangChain4j-preview-41254a8f39-1/google-adk-langchain4j-LangChain4j-preview-41254a8f39-1.pom]}}
{{Downloading from central:
[https://repo.maven.apache.org/maven2/com/github/enola-dev/adk-java/google-adk-langchain4j/LangChain4j-preview-41254a8f39-1/google-adk-langchain4j-LangChain4j-preview-41254a8f39-1.pom]}}
{{[INFO]
--------------------------------------------------------------------------------------------------------------------------}}
{{[INFO] BUILD FAILURE}}
{{[INFO]
--------------------------------------------------------------------------------------------------------------------------}}
{{[INFO] Total time: 0.885 s}}
{{[INFO] Finished at: 2025-06-08T10:40:05+02:00}}
{{[INFO]
--------------------------------------------------------------------------------------------------------------------------}}
{{[ERROR] Failed to execute goal on project langchain4j: Could not collect
dependencies for project dev.enola.adk:langchain4j:jar:0.0.1-SNAPSHOT}}
{{[ERROR] Failed to read artifact descriptor for
com.github.enola-dev.adk-java:google-adk-langchain4j:jar:LangChain4j-preview-41254a8f39-1}}
{{[ERROR] Caused by: The following artifacts could not be resolved:
com.github.enola-dev.adk-java:google-adk-langchain4j:pom:LangChain4j-preview-41254a8f39-1
(absent): Could not transfer artifact
com.github.enola-dev.adk-java:google-adk-langchain4j:pom:LangChain4j-preview-41254a8f39-1
from/to jitpack.io ([https://jitpack.io):|https://jitpack.io)/] HTTP Status:
500}}
{{[ERROR] : Failed to collect dependencies at
com.github.enola-dev.adk-java:google-adk-langchain4j:jar:LangChain4j-preview-41254a8f39-1}}
{{[ERROR] -> [Help 1]}}
{{[ERROR]}}
{{[ERROR] To see the full stack trace of the errors, re-run Maven with the '-e'
switch}}
{{[ERROR] Re-run Maven using the '-X' switch to enable verbose output}}
{{[ERROR]}}
{{[ERROR] For more information about the errors and possible solutions, please
read the following articles:}}
{{[ERROR] [Help 1]
[http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException]}}
I'm assuming that you'll agree that this doesn't seem right, and should be
considered a fairly high priority (blocking?) issue? I haven't debugged it, but
if I had to venture any guess, it would be that Maven 4.0.0 RC3 may be sending
along some (new or different) HTTP header causing JitPack to fall flat on its
face and trigger that 500 on their end?
[~glaforge] FYI
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
