Build error "AptContext has not been created" #795
Comments
|
Hi @kdubb, is there a way for me to replicate the issue? |
|
@metacosm Sorry for not responding. I thought I had. Yes QOSDK We are using the Quarkus platform BOM and Java 17. |
|
Would you be able to share your model since it seems to happen during CRD generation? |
|
@metacosm You're onto something here. We have to subprojects in a Gradle build that share a common "operators" dependency. One is a trust operator for generating certificate bundles and projecting them into needed namespaces handling rotation; it's pretty simple. The other is a Vault operator that manages Vault items required by our services; it's much more in-depth and has a lot of model objects. I'm just realizing that the Vault operator project is where we get the failure. If I attempt to build the simpler trust operator project it builds fine with no error. Our build is scattered across common deps, a common operator dep and then the operator projects themselves; it won't be easy to rip it apart and get it to build in a manner I can share. Any thoughts, based on the stacktrace and this new information, on what exactly might be causing this? Remember it worked with previous Q and QOSDK versions (which we're attempting to move off of). So it must be a change introduced after this setup
|
|
@metacosm By deleting model files until I don't get the error, I was able to narrow it down to a "spec" class that has multiple properties derived from the same base class. E.g. (in kotlin) abstract class Config {}
class SomeConfig: Config {}
class OtherConfig: Config {}
class SomeSpec(
val someConfig: SomeConfig?
val otherConfig: OtherConfig?
)If I remove either |
|
Note that if I change one of the properties to use a different class hierarchy it does not produce the error... E.g. (in kotlin) abstract class AConfig {}
class SomeConfig: AConfig {}
abstract class BConfig {}
class OtherConfig: BConfig {}
class SomeSpec(
val someConfig: SomeConfig?
val otherConfig: OtherConfig?
) |
|
Just to make sure, you're not locking the fabric8 version anymore, right? |
|
No not locked anymore. Currently testing with Q/3.7.2 and QOSDK/6.6.3 |
|
The issue happens because IMHO, |
|
Thank you, @iocanel! |
|
Any update on this, @iocanel? |
|
@iocanel Any news? Sorry to ping again, but this has stopped us for a while. |
|
@kdubb: created sundrio/sundrio#472 |
|
@iocanel Do you know if this has landed in Quarkus, if so, what version? |
|
Hi @kdubb, is this still an issue? |
With 6.5.0 I am getting a the following error listed below.
This is with our project using the sdk aligned
Quarkus 3.6.4.Previously, using
6.4.0withQuarkus 3.5.3(and the Fabric8 client version locked to6.7.2) we weren't getting any issue during the build.The text was updated successfully, but these errors were encountered: