Pasquale Congiusti

Thanks for the feedback @astefanutti. I've just tested with `1.10-nightly` and I confirm the indefinite reconciliation loop has been fixed: ``` camel-k-operator-74d899c876-ns2zx camel-k-operator {"level":"info","ts":1657702227.6277504,"logger":"camel-k.controller.integration","msg":"Reconciling Integration","request-namespace":"default","request-name":"it2"} camel-k-operator-74d899c876-ns2zx camel-k-operator {"level":"info","ts":1657702227.955836,"logger":"camel-k.controller.integration","msg":"Reconciling Integration","request-namespace":"default","request-name":"it3"} camel-k-operator-74d899c876-ns2zx...

I think we don't support Java because the joor dependency. @astefanutti can you confirm please?

Yeah, it seems it is hardcoded. I'm marking this as a feature, feel free to have a look and contribute.

I think we should pick the artifacts from staging, when the reference is present, otherwise it must take it from central. Or am I missing something?

This is similar to #3389 . The problem is that we don't set an upper limit for retries in the reconciliation loop (we probably do it only for the `Build`...

We have no documentation related to that platform unfortunately. Contributions are very welcome.

Just assigned to you. Please, let us know if you need any help.

I think some possible way to fix it is to scan the log provided from the builder. However, I'm just noticing a more general scenario could be covered by #3149....

Thanks @phantomjinx. I was trying to think a simple approach to parse the log, capture the kind of error and bubble up into the Builder error conditions. However, for the...

> Can't we verify the validity of any requested camel artifacts by attempting to look them up in the catalog, instead of parsing logs? Yeah, it's a very good idea....