-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Issues with module-info after upgrading to 6.9.0 #5520
Comments
This relates to the change to add an edit/toBuilder method to each model object. I unwittingly introduced a split package. The simplest change would be to move the .api packages from core to common. @manusa @rohanKanojia any objections? |
This change will be transparent to the end user, right? If yes, no objection from my side. |
It should be. core already depends on common, and I wouldn't expect anyone to complain if common got a little larger. |
Looking at this more closely, it's not a split package problem. It's an issue with the osgi bundling - having the builder package still listed in core is copying the classes from common. |
Describe the bug
We are previously on version 6.7.2 and we are trying to uptake 6.9.0
But our builds are failing with below error
This is our module-info.java
Fabric8 Kubernetes Client version
6.9.0
Steps to reproduce
Expected behavior
Build should be successful
Runtime
other (please specify in additional context)
Kubernetes API Server version
1.25.3@latest
Environment
macOS
Fabric8 Kubernetes Client Logs
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: