You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2023/03/28 05:32:00 UTC
[jira] [Commented] (CAMEL-19204) Generate component configurer case statements for Java 17
[ https://issues.apache.org/jira/browse/CAMEL-19204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17705805#comment-17705805 ]
Claus Ibsen commented on CAMEL-19204:
-------------------------------------
It makes backporting harder as the generated code cannot be cherry picked to 3.x. Lets wait until 3.21 is released and look at this in 6 months.
> Generate component configurer case statements for Java 17
> ---------------------------------------------------------
>
> Key: CAMEL-19204
> URL: https://issues.apache.org/jira/browse/CAMEL-19204
> Project: Camel
> Issue Type: Improvement
> Components: camel-package-maven-plugin
> Reporter: Steve Storck
> Priority: Minor
> Attachments: PropertyConfigurerGenerator.java
>
>
> [~davsclaus] - here's a sort of proposal:
> Some minor edits to {{org.apache.camel.maven.packaging.PropertyConfigurerGenerator}} will generate the case statements in the Java 17 style. I am proposing this, rather than simply doing it and submitting a pull request, because this affects a lot of things. But, since Camel has moved to Java 17 for version 4, it might be good to update how generated code looks, so that it conforms to the more modern standard. I also did a bit of code cleanup in the class which could also be kept or discarded, depending on what you think about it.
> I am attaching the modified class to this ticket. Should this change be introduced? Since it affects so much, is there a preferred way of doing this?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)