oscerd commented on PR #27778:
URL: https://github.com/apache/camel/pull/27778#issuecomment-6163536216
The `build (17, false)` failure here is the main-vs-4.18.x annotation
divergence, not a flake.
```
TelegramConfiguration.java:[69,44] cannot find symbol
TelegramConfiguration.java:[75,67] cannot find symbol
symbol: method insecureValue()
symbol: method security()
```
`@UriParam` gained `security()` and `insecureValue()` after 4.18.x. Checking
`core/camel-api/src/generated/java/org/apache/camel/spi/UriParam.java` on each
branch — note it is under `src/generated`, not `src/main` — `insecureValue`
appears twice on `main` and on `camel-4.22.x`, and **zero times on
`camel-4.18.x`**. So this line cannot compile there:
```java
label = "consumer,security", defaultValue = "true", security =
"insecure:dev", insecureValue = "false"
```
The 4.18.x equivalent is to drop both attributes and mark the option `secret
= true` instead. That also changes the generated catalog JSON, which in this PR
still carries `"security": "insecure:dev", "insecureValue": "false"` in both
the component and catalog copies, so it needs a regen after the annotation
change.
We have that version already prepared and pushed, if it saves you the round
trip: **`oscerd:backport/27716-to-camel-4.18.x`** at `18ae654b9e63` — `secret =
true`, no insecure marker, regenerated, reactor green, 101 tests. It also
resolves the two conflicts this backport has against 4.18.x, in
`telegram-component.adoc` and `TelegramWebhookCallTest`, which is why it is not
a straight cherry-pick.
I have not pushed anything to your branch and will not. Either cherry-pick
from ours, or say the word and I will open it as a separate PR and close
whichever of the two you prefer.
Unrelated to this PR but worth flagging while you are here: **#27777 and
#27781 are both open against `camel-4.22.x` for the same backport** — yours and
ours. One should be closed; I am happy for it to be ours.
_Claude Code on behalf of oscerd_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
