-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Ensure that quarkus-kubernetes does not pollute the runtime classpath #15716
Conversation
Just to clarify, |
Yes, exactly |
Actually, I still need to try something |
Tried what I had in mind and it works just fine |
Some tests are failing :( |
I guess it's a compile dependency which isn't then provided at runtime. Not isolated enough. |
I thought that adding
to
and I don't see why... |
Because it appears as a transitive dependency. Only direct |
I am sure I am missing something from what you described, but I don't really know how to solve this case TBH... If there is some way I can include |
You haven't actually added that dependency to the |
That is what I am trying locally and unfortunately I am seeing the same error. |
I'll have a look into this a bit later today. |
I pushed what I am doing locally as well. |
I'm looking as well to try and understand what is going on. |
Is farbik8 client necessary to build the internal runtime module? |
Yes, unfortunately it is |
Looking into it a little more closely, it seems that this is caused by the fact that |
Doesn't it mean that the fabrik8 client is actually required at runtime? At least from the classloading perspective? |
From a classloader perspective, yes. However the problem is this: When I simple do |
There is probably a horrible hack I can do to make it work, let me check |
It didn't work. I am really baffled by this because the only place this fails is in the |
I think I know why this is happening... |
This is done to align the Quarkus prod mode test with the regular build and is actually necessary to make the overcome classloading issues that only with the QuarkusProdModeTest and the kubernetes-extension
It should now be OK |
I also added a test to make sure this does not happen again |
Great @geoand, thanks! |
👍🏼 |
Fixes: #15705