-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JitPack build for main failed #51
Comments
I cloned petitparser/java-petitparser and ran Here is the error message from the build.log: FWIW, googling brought up this: Reading this, maybe JitPack needs to be told somehow to use Java 11? It used Java 8 for the build. However, as you may have noted, I am somewhat out of my depth here. Cheers, |
Maybe it is a general JitPack problem? Cheers, |
I've increased the JavaSDK version to 8 and then 17, but now there is a different error:
|
No updates about this issue ? |
I am not familiar with Maven or JitPack, happy to merge a pull request if somebody has an idea how to fix the issue? |
Sorry for the duplicate issue. I hope I can make it up to you with a pull request for your main branch that fixes it. I added Maven Wrapper so you can now choose the version of Maven to build with. You can see the working version here. |
It looks like the wrapper fixes this. Thank you! |
You're very welcome. |
I would like to use the latest code in the main branch in a Maven project. I tried to get it from https://jitpack.io/#petitparser/java-petitparser using the following in pom.xlm
However, I get the following error:
[ERROR] Failed to execute goal on project learning-petitparser: Could not resolve dependencies for project com.modelligent:learning-petitparser:jar:1.0.0-SNAPSHOT: Could not find artifact com.github.petitparser:java-petitparser:jar:main-1f87c1e664-1 in jitpack.io (https://jitpack.io) -> [Help 1]
It looks like the last build ran into a failure:
https://jitpack.io/com/github/petitparser/java-petitparser/main-1f87c1e664-1/build.log
Cheers,
Bernhard
The text was updated successfully, but these errors were encountered: