-
Notifications
You must be signed in to change notification settings - Fork 12
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
Doesn't work out-of-the-box #315
Comments
Can't reproduce for now .. Let's meet tomorrow to check that (with the new version I'll release today) |
hmmmm 🤔 pretty wierd. I'll deep dive this tonight (I can't meet tomorrow cause I'm in vacation). I compared the logs in case of failure and in case of success and success logs display these lines in addition:
These lines are not present in case of failure. |
I tried with Java 8 but java 11 is the minimum version ( I tried with Java 17 but it seems an issue already exists for that (#90) I tried with an empty local maven repository, but same result. For context, I use asdfvm to manage java versions on my laptop. Do you think the problem can come from this tool ? Could you copy/paste here the result of your |
It seems to come from class loader that loads jar in a certain order. In case of failure, this dependency is loaded first:
instead of:
|
I think this issue has to be re-open @Riduidel because I still have a problem with the release 0.1.9 :
The |
@Riduidel could you copy/paste the result of I will install the exact same version than you to try on my side. |
Ok, my suspicions are correct... the problem is related to the version of maven. Maven 3.8.1 et 3.8.2 has the same problem, but since 3.8.3 the problem is not present anymore. Maybe it could appear in the documentation as a pre-requisite to avoid others users to search for hours or even days 😉 |
Initiate the project with:
Then just build:
The interesting part of the log seems to be (Complete log bellow):
It seems
jakarta.enterprise:jakarta.enterprise.cdi-api:jar:2.0.2
is conflicting withjavax.enterprise:cdi-api:jar:2.0.SP1
but not really sure.Thanks for your support.
Detailed logs:
The text was updated successfully, but these errors were encountered: