[jira] [Created] (CAMEL-21283) Regression: cannot use camel-version in combination of maven repositories in Camel Jbang cli
Aurélien Pupier created CAMEL-21283: --- Summary: Regression: cannot use camel-version in combination of maven repositories in Camel Jbang cli Key: CAMEL-21283 URL: https://issues.apache.org/jira/browse/CAMEL-21283 Project: Camel Issue Type: Bug Components: camel-jbang Affects Versions: 4.8.0 Reporter: Aurélien Pupier Fix For: 4.8.1 using --camel-version and a providing a specific Maven repository is no more posible with Camel JBang CLI when camel-version and is 4.7- included. This is due to the renaming of --repos transfomed to --repository without transforming the parameter when the new process for another camel-version is used. It is affecting only Run and export as they are the only commands for which it was renamed, all other commands remained with --repos (which is leading to not cogherent naming. This renaming was initially done in an effort to be able to provide parameter using style --repository=xxx --repository=yyy instead of --repos=xxx,yyy but it was already reverted during 4.8 development, so we need to use --repository=xxx,yyy making the singular instead of plural not a good fit anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-21283) Regression: cannot use camel-version in combination of maven repositories in Camel Jbang cli
[ https://issues.apache.org/jira/browse/CAMEL-21283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aurélien Pupier reassigned CAMEL-21283: --- Assignee: Aurélien Pupier > Regression: cannot use camel-version in combination of maven repositories in > Camel Jbang cli > > > Key: CAMEL-21283 > URL: https://issues.apache.org/jira/browse/CAMEL-21283 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.8.0 >Reporter: Aurélien Pupier >Assignee: Aurélien Pupier >Priority: Major > Fix For: 4.8.1 > > > using --camel-version and a providing a specific Maven repository is no more > posible with Camel JBang CLI when camel-version and is 4.7- included. > This is due to the renaming of --repos transfomed to --repository without > transforming the parameter when the new process for another camel-version is > used. > It is affecting only Run and export as they are the only commands for which > it was renamed, all other commands remained with --repos (which is leading to > not cogherent naming. > This renaming was initially done in an effort to be able to provide parameter > using style --repository=xxx --repository=yyy instead of --repos=xxx,yyy but > it was already reverted during 4.8 development, so we need to use > --repository=xxx,yyy making the singular instead of plural not a good fit > anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-21283) Regression: cannot use camel-version in combination of maven repositories in Camel Jbang cli
[ https://issues.apache.org/jira/browse/CAMEL-21283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-21283 started by Aurélien Pupier. --- > Regression: cannot use camel-version in combination of maven repositories in > Camel Jbang cli > > > Key: CAMEL-21283 > URL: https://issues.apache.org/jira/browse/CAMEL-21283 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.8.0 >Reporter: Aurélien Pupier >Assignee: Aurélien Pupier >Priority: Major > Fix For: 4.8.1 > > > using --camel-version and a providing a specific Maven repository is no more > posible with Camel JBang CLI when camel-version and is 4.7- included. > This is due to the renaming of --repos transfomed to --repository without > transforming the parameter when the new process for another camel-version is > used. > It is affecting only Run and export as they are the only commands for which > it was renamed, all other commands remained with --repos (which is leading to > not cogherent naming. > This renaming was initially done in an effort to be able to provide parameter > using style --repository=xxx --repository=yyy instead of --repos=xxx,yyy but > it was already reverted during 4.8 development, so we need to use > --repository=xxx,yyy making the singular instead of plural not a good fit > anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21279) camel-jbang - Export using custom kamelets should not add not needed kamelet JARs
[ https://issues.apache.org/jira/browse/CAMEL-21279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885091#comment-17885091 ] Claus Ibsen edited comment on CAMEL-21279 at 9/27/24 6:48 AM: -- TODO: exporting with custom kamelets in same folder, should be moved into kamelets folder. TODO: kamelets is created as a file and not dir *DONE* TODO: camel-kamelet in pom.xml TODO: remove camel-kamelets-catalog in pom.xml TODO: only include camel-kamelets if using any of the ASF kamelets was (Author: davsclaus): TODO: exporting with custom kamelets in same folder, should be moved into kamelets folder. TODO: kamelets is created as a file and not dir > camel-jbang - Export using custom kamelets should not add not needed kamelet > JARs > - > > Key: CAMEL-21279 > URL: https://issues.apache.org/jira/browse/CAMEL-21279 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.8.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.8.1, 4.9.0 > > > There seems to be that camel-kamelets-catalog and camel-kamelets-util JARs > are added even if they are not in use due to using custom kamelets. > We should trim down. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21282) camel-file: allow creating folders one by one
[ https://issues.apache.org/jira/browse/CAMEL-21282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885242#comment-17885242 ] Sven commented on CAMEL-21282: -- Yes currently we're still using camel-file. We plan to move to azure-files for which we detected the other issue that's now fixed :) > camel-file: allow creating folders one by one > - > > Key: CAMEL-21282 > URL: https://issues.apache.org/jira/browse/CAMEL-21282 > Project: Camel > Issue Type: Wish > Components: camel-file >Affects Versions: 4.8.0 >Reporter: Sven >Priority: Major > Attachments: image-2024-09-26-17-58-10-424.png > > > We are using camel-file to write to an Azure File Share, but this fails > sometimes because our routes can create files in nested folders. > This works fine for a Windows share but Azure shares apparently don't support > creating multiple folders at once. > The code shows it only does this iteratively if there are permissions set but > the file share doesn't support Posix (we're running in Windows), setting > permissions throws an UnsupportedOperationException. > From org.apache.camel.component.file.FileOperations: > !image-2024-09-26-17-58-10-424.png|width=771,height=308! > > would it be possible to add a parameter to have autoCreate create folders in > parts, as is done when a permission is set? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21283) Regression: cannot use camel-version in combination of maven repositories in Camel Jbang cli
[ https://issues.apache.org/jira/browse/CAMEL-21283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aurélien Pupier updated CAMEL-21283: Description: using _camel-version_ and a providing a specific Maven repository is no more posible with Camel JBang CLI when camel-version and is 4.7- included. This is due to the renaming of --repos transfomed to --repository without transforming the parameter when the new process for another camel-version is used. It is affecting only Run and export as they are the only commands for which it was renamed, all other commands remained with --repos (which is leading to not cogherent naming. This renaming was initially done in an effort to be able to provide parameter using style --repository=xxx --repository=yyy instead of --repos=xxx,yyy but it was already reverted during 4.8 development, so we need to use --repository=xxx,yyy making the singular instead of plural not a good fit anymore. was: using --camel-version and a providing a specific Maven repository is no more posible with Camel JBang CLI when camel-version and is 4.7- included. This is due to the renaming of --repos transfomed to --repository without transforming the parameter when the new process for another camel-version is used. It is affecting only Run and export as they are the only commands for which it was renamed, all other commands remained with --repos (which is leading to not cogherent naming. This renaming was initially done in an effort to be able to provide parameter using style --repository=xxx --repository=yyy instead of --repos=xxx,yyy but it was already reverted during 4.8 development, so we need to use --repository=xxx,yyy making the singular instead of plural not a good fit anymore. > Regression: cannot use camel-version in combination of maven repositories in > Camel Jbang cli > > > Key: CAMEL-21283 > URL: https://issues.apache.org/jira/browse/CAMEL-21283 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.8.0 >Reporter: Aurélien Pupier >Assignee: Aurélien Pupier >Priority: Major > Fix For: 4.8.1 > > > using _camel-version_ and a providing a specific Maven repository is no more > posible with Camel JBang CLI when camel-version and is 4.7- included. > This is due to the renaming of --repos transfomed to --repository without > transforming the parameter when the new process for another camel-version is > used. > It is affecting only Run and export as they are the only commands for which > it was renamed, all other commands remained with --repos (which is leading to > not cogherent naming. > This renaming was initially done in an effort to be able to provide parameter > using style --repository=xxx --repository=yyy instead of --repos=xxx,yyy but > it was already reverted during 4.8 development, so we need to use > --repository=xxx,yyy making the singular instead of plural not a good fit > anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21283) Regression: cannot use camel-version in combination of maven repositories in Camel Jbang cli
[ https://issues.apache.org/jira/browse/CAMEL-21283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aurélien Pupier updated CAMEL-21283: Description: using _camel-version_ and a providing a specific Maven repository is no more posible with Camel JBang CLI when camel-version and is 4.7- included. This is due to the renaming of --repos transfomed to --repository without transforming the parameter when the new process for another camel-version is used. It is affecting only Run and export as they are the only commands for which it was renamed, all other commands remained with --repos (which is leading to not coherent naming between commands). This renaming was initially done in an effort to be able to provide parameter using style --repository=xxx --repository=yyy instead of --repos=xxx,yyy but it was already reverted during 4.8 development, so we need to use --repository=xxx,yyy making the singular instead of plural not a good fit anymore. was: using _camel-version_ and a providing a specific Maven repository is no more posible with Camel JBang CLI when camel-version and is 4.7- included. This is due to the renaming of --repos transfomed to --repository without transforming the parameter when the new process for another camel-version is used. It is affecting only Run and export as they are the only commands for which it was renamed, all other commands remained with --repos (which is leading to not cogherent naming. This renaming was initially done in an effort to be able to provide parameter using style --repository=xxx --repository=yyy instead of --repos=xxx,yyy but it was already reverted during 4.8 development, so we need to use --repository=xxx,yyy making the singular instead of plural not a good fit anymore. > Regression: cannot use camel-version in combination of maven repositories in > Camel Jbang cli > > > Key: CAMEL-21283 > URL: https://issues.apache.org/jira/browse/CAMEL-21283 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.8.0 >Reporter: Aurélien Pupier >Assignee: Aurélien Pupier >Priority: Major > Fix For: 4.8.1 > > > using _camel-version_ and a providing a specific Maven repository is no more > posible with Camel JBang CLI when camel-version and is 4.7- included. > This is due to the renaming of --repos transfomed to --repository without > transforming the parameter when the new process for another camel-version is > used. > It is affecting only Run and export as they are the only commands for which > it was renamed, all other commands remained with --repos (which is leading to > not coherent naming between commands). > This renaming was initially done in an effort to be able to provide parameter > using style --repository=xxx --repository=yyy instead of --repos=xxx,yyy but > it was already reverted during 4.8 development, so we need to use > --repository=xxx,yyy making the singular instead of plural not a good fit > anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21282) camel-file: allow creating folders one by one
[ https://issues.apache.org/jira/browse/CAMEL-21282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885268#comment-17885268 ] Claus Ibsen commented on CAMEL-21282: - Well so are you asking to add some option to camel-file until you migrate to azure-files by which time you dont need the "hack" in camel-file anymore ? > camel-file: allow creating folders one by one > - > > Key: CAMEL-21282 > URL: https://issues.apache.org/jira/browse/CAMEL-21282 > Project: Camel > Issue Type: Wish > Components: camel-file >Affects Versions: 4.8.0 >Reporter: Sven >Priority: Major > Attachments: image-2024-09-26-17-58-10-424.png > > > We are using camel-file to write to an Azure File Share, but this fails > sometimes because our routes can create files in nested folders. > This works fine for a Windows share but Azure shares apparently don't support > creating multiple folders at once. > The code shows it only does this iteratively if there are permissions set but > the file share doesn't support Posix (we're running in Windows), setting > permissions throws an UnsupportedOperationException. > From org.apache.camel.component.file.FileOperations: > !image-2024-09-26-17-58-10-424.png|width=771,height=308! > > would it be possible to add a parameter to have autoCreate create folders in > parts, as is done when a permission is set? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21279) camel-jbang - Export using custom kamelets should not add not needed kamelet JARs
[ https://issues.apache.org/jira/browse/CAMEL-21279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885091#comment-17885091 ] Claus Ibsen edited comment on CAMEL-21279 at 9/27/24 11:20 AM: --- TODO: exporting with custom kamelets in same folder, should be moved into kamelets folder. *DONE* TODO: kamelets is created as a file and not dir *DONE* TODO: camel-kamelet is missing in pom.xml *DONE* TODO: remove camel-kamelets-catalog in pom.xml *DONE* TODO: only include camel-kamelets if using any of the ASF kamelets *DONE* was (Author: davsclaus): TODO: exporting with custom kamelets in same folder, should be moved into kamelets folder. *DONE* TODO: kamelets is created as a file and not dir *DONE* TODO: camel-kamelet in pom.xml *DONE* TODO: remove camel-kamelets-catalog in pom.xml *DONE* TODO: only include camel-kamelets if using any of the ASF kamelets *DONE* > camel-jbang - Export using custom kamelets should not add not needed kamelet > JARs > - > > Key: CAMEL-21279 > URL: https://issues.apache.org/jira/browse/CAMEL-21279 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.8.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.8.1, 4.9.0 > > > There seems to be that camel-kamelets-catalog and camel-kamelets-util JARs > are added even if they are not in use due to using custom kamelets. > We should trim down. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21285) [camel-jbang] Error exporting from different directory
[
https://issues.apache.org/jira/browse/CAMEL-21285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21285:
Priority: Minor (was: Major)
> [camel-jbang] Error exporting from different directory
> ---
>
> Key: CAMEL-21285
> URL: https://issues.apache.org/jira/browse/CAMEL-21285
> Project: Camel
> Issue Type: Bug
>Affects Versions: 4.9.0
>Reporter: Pasquale Congiusti
>Assignee: Pasquale Congiusti
>Priority: Minor
> Fix For: 4.9.0
>
>
> While working on some strengthening export test to validate the output I
> bumped into this bug:
> {code}
> camel export tmp/test.yaml --runtime quarkus --gav o:a:1.0.0 --dir ceq
> {code}
> would produce a wrong export as it correctly set the route into
> src/main/resources/camel but it wrongly set the application.properties with
> camel.main.routes-include-pattern=camel/tmp/test.yaml
> The result is an application that fails to execute.
> The same problem happens with Java which are distributed to a different
> folder and a different application properties configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21285) [camel-jbang] Error exporting from different directory
[
https://issues.apache.org/jira/browse/CAMEL-21285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885319#comment-17885319
]
Claus Ibsen commented on CAMEL-21285:
-
It was not intended to export from any arbitrary folder, but to export from
current folder. (or what was run previously).
Its just getting a bit more and more "messy" with all these relative / absolute
paths.
> [camel-jbang] Error exporting from different directory
> ---
>
> Key: CAMEL-21285
> URL: https://issues.apache.org/jira/browse/CAMEL-21285
> Project: Camel
> Issue Type: Bug
>Affects Versions: 4.9.0
>Reporter: Pasquale Congiusti
>Assignee: Pasquale Congiusti
>Priority: Minor
> Fix For: 4.9.0
>
>
> While working on some strengthening export test to validate the output I
> bumped into this bug:
> {code}
> camel export tmp/test.yaml --runtime quarkus --gav o:a:1.0.0 --dir ceq
> {code}
> would produce a wrong export as it correctly set the route into
> src/main/resources/camel but it wrongly set the application.properties with
> camel.main.routes-include-pattern=camel/tmp/test.yaml
> The result is an application that fails to execute.
> The same problem happens with Java which are distributed to a different
> folder and a different application properties configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21283) Regression: cannot use camel-version in combination of maven repositories in Camel Jbang cli
[ https://issues.apache.org/jira/browse/CAMEL-21283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aurélien Pupier resolved CAMEL-21283. - Resolution: Fixed > Regression: cannot use camel-version in combination of maven repositories in > Camel Jbang cli > > > Key: CAMEL-21283 > URL: https://issues.apache.org/jira/browse/CAMEL-21283 > Project: Camel > Issue Type: Bug > Components: camel-jbang >Affects Versions: 4.8.0 >Reporter: Aurélien Pupier >Assignee: Aurélien Pupier >Priority: Major > Fix For: 4.8.1 > > > using _camel-version_ and a providing a specific Maven repository is no more > posible with Camel JBang CLI when camel-version and is 4.7- included. > This is due to the renaming of --repos transfomed to --repository without > transforming the parameter when the new process for another camel-version is > used. > It is affecting only Run and export as they are the only commands for which > it was renamed, all other commands remained with --repos (which is leading to > not coherent naming between commands). > This renaming was initially done in an effort to be able to provide parameter > using style --repository=xxx --repository=yyy instead of --repos=xxx,yyy but > it was already reverted during 4.8 development, so we need to use > --repository=xxx,yyy making the singular instead of plural not a good fit > anymore. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21284) camel-clickup: remove dependency from camel-webhook
[
https://issues.apache.org/jira/browse/CAMEL-21284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolò Scarpa updated CAMEL-21284:
--
Description:
The new {{camel-clickup}} component relies on the {{camel-webhook}}
(meta-)component for providing webhook functionality. This is actually the
[encouraged
design|https://camel.apache.org/components/4.8.x/webhook-component.html] for
implementing new webhooks capable components, but it's a bit hacky since the
specialized component won't be actually used as an endpoint, but it would be
rather used as the _delegate_ for the {{camel-webhook}} component.
See if it's possibile to make camel-webhook reusable by other components, so no
code duplication is needed to implement webhook functionality.
Remove the {{camel-webook}} dependency from this component and implement the
actual webhook behavior directly in the {{camel-clickup}} component.
The goal is to make clickup a first-class component that is like others and
also tooling / dsl friendly.
was:
The new {{camel-clickup}} component relies on the {{camel-webhook}}
(meta-)component for providing webhook functionality. This is actually the
encouraged design (see
[documentation|https://camel.apache.org/components/4.8.x/webhook-component.html])
for implementing new webhooks capable components, but it's a bit hacky since
the specialized component won't be actually used as an endpoint, but it would
be rather used as the _delegate_ for the {{camel-webhook}} component.
See if it's possibile to make camel-webhook reusable by other components, so no
code duplication is needed to implement webhook functionality.
Remove the {{camel-webook}} dependency from this component and implement the
actual webhook behavior directly in the {{camel-clickup}} component.
The goal is to make clickup a first-class component that is like others and
also tooling / dsl friendly.
> camel-clickup: remove dependency from camel-webhook
> ---
>
> Key: CAMEL-21284
> URL: https://issues.apache.org/jira/browse/CAMEL-21284
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 4.9.0
>Reporter: Nicolò Scarpa
>Priority: Major
> Fix For: 4.9.0
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> The new {{camel-clickup}} component relies on the {{camel-webhook}}
> (meta-)component for providing webhook functionality. This is actually the
> [encouraged
> design|https://camel.apache.org/components/4.8.x/webhook-component.html] for
> implementing new webhooks capable components, but it's a bit hacky since the
> specialized component won't be actually used as an endpoint, but it would be
> rather used as the _delegate_ for the {{camel-webhook}} component.
> See if it's possibile to make camel-webhook reusable by other components, so
> no code duplication is needed to implement webhook functionality.
> Remove the {{camel-webook}} dependency from this component and implement the
> actual webhook behavior directly in the {{camel-clickup}} component.
> The goal is to make clickup a first-class component that is like others and
> also tooling / dsl friendly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work started] (CAMEL-21278) Camel-Jbang Kubernetes Plugin: clean-up to new trait model and the tests
[ https://issues.apache.org/jira/browse/CAMEL-21278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-21278 started by Gaelle Fournier. --- > Camel-Jbang Kubernetes Plugin: clean-up to new trait model and the tests > > > Key: CAMEL-21278 > URL: https://issues.apache.org/jira/browse/CAMEL-21278 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.x >Reporter: Gaelle Fournier >Assignee: Gaelle Fournier >Priority: Major > Fix For: 4.9.0 > > > This is a follow-up from https://issues.apache.org/jira/browse/CAMEL-21152. > Clean-up identified: > * remove unused parameters and setters/getters > * add some model builder > * refactor the tests to improve the performance -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21285) [camel-jbang] Error exporting from different directory
[
https://issues.apache.org/jira/browse/CAMEL-21285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21285:
Component/s: camel-jbang
> [camel-jbang] Error exporting from different directory
> ---
>
> Key: CAMEL-21285
> URL: https://issues.apache.org/jira/browse/CAMEL-21285
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Pasquale Congiusti
>Assignee: Pasquale Congiusti
>Priority: Minor
> Fix For: 4.9.0
>
>
> While working on some strengthening export test to validate the output I
> bumped into this bug:
> {code}
> camel export tmp/test.yaml --runtime quarkus --gav o:a:1.0.0 --dir ceq
> {code}
> would produce a wrong export as it correctly set the route into
> src/main/resources/camel but it wrongly set the application.properties with
> camel.main.routes-include-pattern=camel/tmp/test.yaml
> The result is an application that fails to execute.
> The same problem happens with Java which are distributed to a different
> folder and a different application properties configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (CAMEL-21285) [camel-jbang] Error exporting from different directory
[
https://issues.apache.org/jira/browse/CAMEL-21285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pasquale Congiusti closed CAMEL-21285.
--
Resolution: Fixed
> [camel-jbang] Error exporting from different directory
> ---
>
> Key: CAMEL-21285
> URL: https://issues.apache.org/jira/browse/CAMEL-21285
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Pasquale Congiusti
>Assignee: Pasquale Congiusti
>Priority: Minor
> Fix For: 4.9.0
>
>
> While working on some strengthening export test to validate the output I
> bumped into this bug:
> {code}
> camel export tmp/test.yaml --runtime quarkus --gav o:a:1.0.0 --dir ceq
> {code}
> would produce a wrong export as it correctly set the route into
> src/main/resources/camel but it wrongly set the application.properties with
> camel.main.routes-include-pattern=camel/tmp/test.yaml
> The result is an application that fails to execute.
> The same problem happens with Java which are distributed to a different
> folder and a different application properties configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21279) camel-jbang - Export using custom kamelets should not add not needed kamelet JARs
[ https://issues.apache.org/jira/browse/CAMEL-21279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885091#comment-17885091 ] Claus Ibsen edited comment on CAMEL-21279 at 9/27/24 9:35 AM: -- TODO: exporting with custom kamelets in same folder, should be moved into kamelets folder. *DONE* TODO: kamelets is created as a file and not dir *DONE* TODO: camel-kamelet in pom.xml *DONE* TODO: remove camel-kamelets-catalog in pom.xml *DONE* TODO: only include camel-kamelets if using any of the ASF kamelets *DONE* was (Author: davsclaus): TODO: exporting with custom kamelets in same folder, should be moved into kamelets folder. *DONE* TODO: kamelets is created as a file and not dir *DONE* TODO: camel-kamelet in pom.xml TODO: remove camel-kamelets-catalog in pom.xml *DONE* TODO: only include camel-kamelets if using any of the ASF kamelets > camel-jbang - Export using custom kamelets should not add not needed kamelet > JARs > - > > Key: CAMEL-21279 > URL: https://issues.apache.org/jira/browse/CAMEL-21279 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.8.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.8.1, 4.9.0 > > > There seems to be that camel-kamelets-catalog and camel-kamelets-util JARs > are added even if they are not in use due to using custom kamelets. > We should trim down. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21284) camel-clickup: remove dependency from camel-webhook
[
https://issues.apache.org/jira/browse/CAMEL-21284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolò Scarpa updated CAMEL-21284:
--
Description:
The new {{camel-clickup}} component relies on the {{camel-webhook}}
(meta-)component for providing webhook functionality. This is actually the
encouraged design
([https://camel.apache.org/components/4.8.x/webhook-component.html]) for
implementing new webhooks capable components, but it's a bit hacky since the
specialized component won't be actually used as an endpoint, but it would be
rather used as the _delegate_ for the {{camel-webhook}} component.
See if it's possibile to make camel-webhook reusable by other components, so no
code duplication is needed to implement webhook functionality.
Remove the {{camel-webook}} dependency from this component and implement the
actual webhook behavior directly in the {{camel-clickup}} component.
The goal is to make clickup a first-class component that is like others and
also tooling / dsl friendly.
was:
The new `camel-clickup` component relies on the `camel-webhook`
(meta-)component for providing webhook functionality. This is actually the
encouraged design
([https://camel.apache.org/components/4.8.x/webhook-component.html]) for
implementing new webhooks capable components, but it's a bit hacky since the
specialized component won't be actually used as an endpoint, but it would be
rather used as the _delegate_ for the `camel-webhook` component.
See if it's possibile to make camel-webhook reusable by other components, so no
code duplication is needed to implement webhook functionality.
Remove the `camel-webook` dependency from this component and implement the
actual webhook behavior directly in the `camel-clickup` component.
The goal is to make clickup a first-class component that is like others and
also tooling / dsl friendly.
> camel-clickup: remove dependency from camel-webhook
> ---
>
> Key: CAMEL-21284
> URL: https://issues.apache.org/jira/browse/CAMEL-21284
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 4.9.0
>Reporter: Nicolò Scarpa
>Priority: Major
> Fix For: 4.9.0
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> The new {{camel-clickup}} component relies on the {{camel-webhook}}
> (meta-)component for providing webhook functionality. This is actually the
> encouraged design
> ([https://camel.apache.org/components/4.8.x/webhook-component.html]) for
> implementing new webhooks capable components, but it's a bit hacky since the
> specialized component won't be actually used as an endpoint, but it would be
> rather used as the _delegate_ for the {{camel-webhook}} component.
> See if it's possibile to make camel-webhook reusable by other components, so
> no code duplication is needed to implement webhook functionality.
> Remove the {{camel-webook}} dependency from this component and implement the
> actual webhook behavior directly in the {{camel-clickup}} component.
> The goal is to make clickup a first-class component that is like others and
> also tooling / dsl friendly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21279) camel-jbang - Export using custom kamelets should not add not needed kamelet JARs
[ https://issues.apache.org/jira/browse/CAMEL-21279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21279. - Resolution: Fixed > camel-jbang - Export using custom kamelets should not add not needed kamelet > JARs > - > > Key: CAMEL-21279 > URL: https://issues.apache.org/jira/browse/CAMEL-21279 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.8.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.8.1, 4.9.0 > > > There seems to be that camel-kamelets-catalog and camel-kamelets-util JARs > are added even if they are not in use due to using custom kamelets. > We should trim down. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21285) [camel-jbang] Error exporting from different directory
[
https://issues.apache.org/jira/browse/CAMEL-21285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885377#comment-17885377
]
Pasquale Congiusti commented on CAMEL-21285:
Yeah. We were already altering the content coming from the .camel-jbang
property file but without taking in consideration any possible extra path. It
should be now fixed with in https://github.com/apache/camel/pull/15743
> [camel-jbang] Error exporting from different directory
> ---
>
> Key: CAMEL-21285
> URL: https://issues.apache.org/jira/browse/CAMEL-21285
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.9.0
>Reporter: Pasquale Congiusti
>Assignee: Pasquale Congiusti
>Priority: Minor
> Fix For: 4.9.0
>
>
> While working on some strengthening export test to validate the output I
> bumped into this bug:
> {code}
> camel export tmp/test.yaml --runtime quarkus --gav o:a:1.0.0 --dir ceq
> {code}
> would produce a wrong export as it correctly set the route into
> src/main/resources/camel but it wrongly set the application.properties with
> camel.main.routes-include-pattern=camel/tmp/test.yaml
> The result is an application that fails to execute.
> The same problem happens with Java which are distributed to a different
> folder and a different application properties configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21286) Add a cache to JAXB object factories on JAXB Marshalling/Fallback converter
[ https://issues.apache.org/jira/browse/CAMEL-21286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885463#comment-17885463 ] Adriano Machado commented on CAMEL-21286: - [~davsclaus], the app is using both JAXB data type and conversions from DOM to JAXB POJOs. Please see attached screenshots with an analysis from an APM tool. I couldn't get the same results by running locally, only coming from the APM tool capturing executions from an OCP cluster. > Add a cache to JAXB object factories on JAXB Marshalling/Fallback converter > --- > > Key: CAMEL-21286 > URL: https://issues.apache.org/jira/browse/CAMEL-21286 > Project: Camel > Issue Type: Improvement > Components: camel-jaxb >Affects Versions: 4.4.3 >Reporter: Adriano Machado >Priority: Major > > Camel is calling `JaxbHelper.getJaxbElementFactoryMethod` and the result is > not being cached. This expensive call on apps with schemas deployed on nested > jars on Spring Boot apps running on Openshift. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21286) Add a cache to JAXB object factories on JAXB Marshalling/Fallback converter
[
https://issues.apache.org/jira/browse/CAMEL-21286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885463#comment-17885463
]
Adriano Machado edited comment on CAMEL-21286 at 9/27/24 7:45 PM:
--
[~davsclaus], the app is using both JAXB data type and conversions from DOM to
JAXB POJOs.
{-}Please see attached screenshots with an analysis from an APM tool{-}. I'm
trying to upload a few screenshots from the APM tool, but Jira is not allowing
me (failing with an internal error).
I couldn't get the same results by running locally, only coming from the APM
tool capturing executions from an OCP cluster.
was (Author: ammachado):
[~davsclaus], the app is using both JAXB data type and conversions from DOM to
JAXB POJOs. Please see attached screenshots with an analysis from an APM tool.
I couldn't get the same results by running locally, only coming from the APM
tool capturing executions from an OCP cluster.
> Add a cache to JAXB object factories on JAXB Marshalling/Fallback converter
> ---
>
> Key: CAMEL-21286
> URL: https://issues.apache.org/jira/browse/CAMEL-21286
> Project: Camel
> Issue Type: Improvement
> Components: camel-jaxb
>Affects Versions: 4.4.3
>Reporter: Adriano Machado
>Priority: Major
>
> Camel is calling `JaxbHelper.getJaxbElementFactoryMethod` and the result is
> not being cached. This expensive call on apps with schemas deployed on nested
> jars on Spring Boot apps running on Openshift.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21286) Add a cache to JAXB object factories on JAXB Marshalling/Fallback converter
[ https://issues.apache.org/jira/browse/CAMEL-21286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885430#comment-17885430 ] Claus Ibsen commented on CAMEL-21286: - Can you tell more what exactly you are doing as this is in camel-jaxb that can be used as "jaxb" data format, or as some legacy JAXB type converter for XML to POJO classes. What is it that makes it expensive, and do you only see this on a fat-jar SB on OCP or would it also be "slow" running local with mvn spring:boot in developer mode. > Add a cache to JAXB object factories on JAXB Marshalling/Fallback converter > --- > > Key: CAMEL-21286 > URL: https://issues.apache.org/jira/browse/CAMEL-21286 > Project: Camel > Issue Type: Improvement > Components: camel-jaxb >Affects Versions: 4.4.3 >Reporter: Adriano Machado >Priority: Major > > Camel is calling `JaxbHelper.getJaxbElementFactoryMethod` and the result is > not being cached. This expensive call on apps with schemas deployed on nested > jars on Spring Boot apps running on Openshift. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21284) camel-clickup: remove dependency from camel-webhook
[ https://issues.apache.org/jira/browse/CAMEL-21284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolò Scarpa updated CAMEL-21284: -- Description: The new `camel-clickup` component relies on the `camel-webhook` (meta-)component for providing webhook functionality. This is actually the encouraged design ([https://camel.apache.org/components/4.8.x/webhook-component.html]) for implementing new webhooks capable components, but it's a bit hacky since the specialized component won't be actually used as an endpoint, but it would be rather used as the _delegate_ for the `camel-webhook` component. See if it's possibile to make camel-webhook reusable by other components, so no code duplication is needed to implement webhook functionality. Remove the `camel-webook` dependency from this component and implement the actual webhook behavior directly in the `camel-clickup` component. The goal is to make clickup a first-class component that is like others and also tooling / dsl friendly. was: The new `camel-clickup` component relies on the `camel-webhook` (meta-)component for providing webhook functionality. This is actually the encouraged design (https://camel.apache.org/components/4.8.x/webhook-component.html) for implementing new webhooks capable components, but it's a bit hacky since the specialized component won't be actually used as an endpoint, but it would be rather used as the _delegate_ for the `camel-webhook` component. Remove the `camel-webook` dependency from this component and implement the actual webhook behavior directly in the `camel-clickup` component. > camel-clickup: remove dependency from camel-webhook > --- > > Key: CAMEL-21284 > URL: https://issues.apache.org/jira/browse/CAMEL-21284 > Project: Camel > Issue Type: Improvement >Affects Versions: 4.9.0 >Reporter: Nicolò Scarpa >Priority: Major > Fix For: 4.9.0 > > Original Estimate: 72h > Remaining Estimate: 72h > > The new `camel-clickup` component relies on the `camel-webhook` > (meta-)component for providing webhook functionality. This is actually the > encouraged design > ([https://camel.apache.org/components/4.8.x/webhook-component.html]) for > implementing new webhooks capable components, but it's a bit hacky since the > specialized component won't be actually used as an endpoint, but it would be > rather used as the _delegate_ for the `camel-webhook` component. > See if it's possibile to make camel-webhook reusable by other components, so > no code duplication is needed to implement webhook functionality. > Remove the `camel-webook` dependency from this component and implement the > actual webhook behavior directly in the `camel-clickup` component. > The goal is to make clickup a first-class component that is like others and > also tooling / dsl friendly. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-21285) [camel-jbang] Error exporting from different directory
Pasquale Congiusti created CAMEL-21285:
--
Summary: [camel-jbang] Error exporting from different directory
Key: CAMEL-21285
URL: https://issues.apache.org/jira/browse/CAMEL-21285
Project: Camel
Issue Type: Bug
Affects Versions: 4.9.0
Reporter: Pasquale Congiusti
Assignee: Pasquale Congiusti
Fix For: 4.9.0
While working on some strengthening export test to validate the output I bumped
into this bug:
{code}
camel export tmp/test.yaml --runtime quarkus --gav o:a:1.0.0 --dir ceq
{code}
would produce a wrong export as it correctly set the route into
src/main/resources/camel but it wrongly set the application.properties with
camel.main.routes-include-pattern=camel/tmp/test.yaml
The result is an application that fails to execute.
The same problem happens with Java which are distributed to a different folder
and a different application properties configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21284) camel-clickup: remove dependency from camel-webhook
Nicolò Scarpa created CAMEL-21284: - Summary: camel-clickup: remove dependency from camel-webhook Key: CAMEL-21284 URL: https://issues.apache.org/jira/browse/CAMEL-21284 Project: Camel Issue Type: Improvement Affects Versions: 4.9.0 Reporter: Nicolò Scarpa Fix For: 4.9.0 The new `camel-clickup` component relies on the `camel-webhook` (meta-)component for providing webhook functionality. This is actually the encouraged design (https://camel.apache.org/components/4.8.x/webhook-component.html) for implementing new webhooks capable components, but it's a bit hacky since the specialized component won't be actually used as an endpoint, but it would be rather used as the _delegate_ for the `camel-webhook` component. Remove the `camel-webook` dependency from this component and implement the actual webhook behavior directly in the `camel-clickup` component. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21276) camel-kamelet - ENV variable name configuration - Can we support underscore for long names
[ https://issues.apache.org/jira/browse/CAMEL-21276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21276. - Resolution: Fixed > camel-kamelet - ENV variable name configuration - Can we support underscore > for long names > -- > > Key: CAMEL-21276 > URL: https://issues.apache.org/jira/browse/CAMEL-21276 > Project: Camel > Issue Type: Improvement > Components: camel-kamelet >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > This is only about kamelets (not general bootstrap configuration when using > SB/Q or camel-main) as that depends on how those runtimes behave. > CAMEL_KAMELET_AWS_S3_SOURCE_BUCKETNAMEORARN > The last option is bucketNameOrArn in the kamelet. But for readability we may > improve camel-kamelet to support both naming styles > CAMEL_KAMELET_AWS_S3_SOURCE_BUCKET_NAME_OR_ARN > CAMEL_KAMELET_AWS_S3_SOURCE_BUCKETNAMEORARN > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21279) camel-jbang - Export using custom kamelets should not add not needed kamelet JARs
[ https://issues.apache.org/jira/browse/CAMEL-21279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885091#comment-17885091 ] Claus Ibsen edited comment on CAMEL-21279 at 9/27/24 8:49 AM: -- TODO: exporting with custom kamelets in same folder, should be moved into kamelets folder. *DONE* TODO: kamelets is created as a file and not dir *DONE* TODO: camel-kamelet in pom.xml TODO: remove camel-kamelets-catalog in pom.xml *DONE* TODO: only include camel-kamelets if using any of the ASF kamelets was (Author: davsclaus): TODO: exporting with custom kamelets in same folder, should be moved into kamelets folder. *DONE* TODO: kamelets is created as a file and not dir *DONE* TODO: camel-kamelet in pom.xml TODO: remove camel-kamelets-catalog in pom.xml TODO: only include camel-kamelets if using any of the ASF kamelets > camel-jbang - Export using custom kamelets should not add not needed kamelet > JARs > - > > Key: CAMEL-21279 > URL: https://issues.apache.org/jira/browse/CAMEL-21279 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.8.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.8.1, 4.9.0 > > > There seems to be that camel-kamelets-catalog and camel-kamelets-util JARs > are added even if they are not in use due to using custom kamelets. > We should trim down. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21284) camel-clickup: remove dependency from camel-webhook
[
https://issues.apache.org/jira/browse/CAMEL-21284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolò Scarpa updated CAMEL-21284:
--
Description:
The new {{camel-clickup}} component relies on the {{camel-webhook}}
(meta-)component for providing webhook functionality. This is actually the
encouraged design (see
[documentation|https://camel.apache.org/components/4.8.x/webhook-component.html])
for implementing new webhooks capable components, but it's a bit hacky since
the specialized component won't be actually used as an endpoint, but it would
be rather used as the _delegate_ for the {{camel-webhook}} component.
See if it's possibile to make camel-webhook reusable by other components, so no
code duplication is needed to implement webhook functionality.
Remove the {{camel-webook}} dependency from this component and implement the
actual webhook behavior directly in the {{camel-clickup}} component.
The goal is to make clickup a first-class component that is like others and
also tooling / dsl friendly.
was:
The new {{camel-clickup}} component relies on the {{camel-webhook}}
(meta-)component for providing webhook functionality. This is actually the
encouraged design
([https://camel.apache.org/components/4.8.x/webhook-component.html]) for
implementing new webhooks capable components, but it's a bit hacky since the
specialized component won't be actually used as an endpoint, but it would be
rather used as the _delegate_ for the {{camel-webhook}} component.
See if it's possibile to make camel-webhook reusable by other components, so no
code duplication is needed to implement webhook functionality.
Remove the {{camel-webook}} dependency from this component and implement the
actual webhook behavior directly in the {{camel-clickup}} component.
The goal is to make clickup a first-class component that is like others and
also tooling / dsl friendly.
> camel-clickup: remove dependency from camel-webhook
> ---
>
> Key: CAMEL-21284
> URL: https://issues.apache.org/jira/browse/CAMEL-21284
> Project: Camel
> Issue Type: Improvement
>Affects Versions: 4.9.0
>Reporter: Nicolò Scarpa
>Priority: Major
> Fix For: 4.9.0
>
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> The new {{camel-clickup}} component relies on the {{camel-webhook}}
> (meta-)component for providing webhook functionality. This is actually the
> encouraged design (see
> [documentation|https://camel.apache.org/components/4.8.x/webhook-component.html])
> for implementing new webhooks capable components, but it's a bit hacky since
> the specialized component won't be actually used as an endpoint, but it would
> be rather used as the _delegate_ for the {{camel-webhook}} component.
> See if it's possibile to make camel-webhook reusable by other components, so
> no code duplication is needed to implement webhook functionality.
> Remove the {{camel-webook}} dependency from this component and implement the
> actual webhook behavior directly in the {{camel-clickup}} component.
> The goal is to make clickup a first-class component that is like others and
> also tooling / dsl friendly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-21285) [camel-jbang] Error exporting from different directory
[
https://issues.apache.org/jira/browse/CAMEL-21285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885367#comment-17885367
]
Claus Ibsen commented on CAMEL-21285:
-
You are welcome to see if a fix can be made somewhat easy. Its maybe to strip
the relative path when files are copied into resource folders. So tmp/foo.yaml
becomes foo.yaml
> [camel-jbang] Error exporting from different directory
> ---
>
> Key: CAMEL-21285
> URL: https://issues.apache.org/jira/browse/CAMEL-21285
> Project: Camel
> Issue Type: Bug
>Affects Versions: 4.9.0
>Reporter: Pasquale Congiusti
>Assignee: Pasquale Congiusti
>Priority: Minor
> Fix For: 4.9.0
>
>
> While working on some strengthening export test to validate the output I
> bumped into this bug:
> {code}
> camel export tmp/test.yaml --runtime quarkus --gav o:a:1.0.0 --dir ceq
> {code}
> would produce a wrong export as it correctly set the route into
> src/main/resources/camel but it wrongly set the application.properties with
> camel.main.routes-include-pattern=camel/tmp/test.yaml
> The result is an application that fails to execute.
> The same problem happens with Java which are distributed to a different
> folder and a different application properties configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-21276) camel-kamelet - ENV variable name configuration - Can we support underscore for long names
[ https://issues.apache.org/jira/browse/CAMEL-21276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-21276: --- Assignee: Claus Ibsen > camel-kamelet - ENV variable name configuration - Can we support underscore > for long names > -- > > Key: CAMEL-21276 > URL: https://issues.apache.org/jira/browse/CAMEL-21276 > Project: Camel > Issue Type: Improvement > Components: camel-kamelet >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > This is only about kamelets (not general bootstrap configuration when using > SB/Q or camel-main) as that depends on how those runtimes behave. > CAMEL_KAMELET_AWS_S3_SOURCE_BUCKETNAMEORARN > The last option is bucketNameOrArn in the kamelet. But for readability we may > improve camel-kamelet to support both naming styles > CAMEL_KAMELET_AWS_S3_SOURCE_BUCKET_NAME_OR_ARN > CAMEL_KAMELET_AWS_S3_SOURCE_BUCKETNAMEORARN > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21276) camel-kamelet - ENV variable name configuration - Can we support underscore for long names
[ https://issues.apache.org/jira/browse/CAMEL-21276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21276: Fix Version/s: 4.9.0 (was: 4.x) > camel-kamelet - ENV variable name configuration - Can we support underscore > for long names > -- > > Key: CAMEL-21276 > URL: https://issues.apache.org/jira/browse/CAMEL-21276 > Project: Camel > Issue Type: Improvement > Components: camel-kamelet >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.9.0 > > > This is only about kamelets (not general bootstrap configuration when using > SB/Q or camel-main) as that depends on how those runtimes behave. > CAMEL_KAMELET_AWS_S3_SOURCE_BUCKETNAMEORARN > The last option is bucketNameOrArn in the kamelet. But for readability we may > improve camel-kamelet to support both naming styles > CAMEL_KAMELET_AWS_S3_SOURCE_BUCKET_NAME_OR_ARN > CAMEL_KAMELET_AWS_S3_SOURCE_BUCKETNAMEORARN > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21282) camel-file: allow creating folders one by one
[ https://issues.apache.org/jira/browse/CAMEL-21282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885270#comment-17885270 ] Sven commented on CAMEL-21282: -- Well in our case yes because we can't use SMB in Azure on containers, but this doesn't negate the fact that camel-file using Azure file share SMB is not isofunctional with using other SMB file shares (due to a restriction on Azure Files). MS already indicated they have no intention of resolving this limitation.. > camel-file: allow creating folders one by one > - > > Key: CAMEL-21282 > URL: https://issues.apache.org/jira/browse/CAMEL-21282 > Project: Camel > Issue Type: Wish > Components: camel-file >Affects Versions: 4.8.0 >Reporter: Sven >Priority: Major > Attachments: image-2024-09-26-17-58-10-424.png > > > We are using camel-file to write to an Azure File Share, but this fails > sometimes because our routes can create files in nested folders. > This works fine for a Windows share but Azure shares apparently don't support > creating multiple folders at once. > The code shows it only does this iteratively if there are permissions set but > the file share doesn't support Posix (we're running in Windows), setting > permissions throws an UnsupportedOperationException. > From org.apache.camel.component.file.FileOperations: > !image-2024-09-26-17-58-10-424.png|width=771,height=308! > > would it be possible to add a parameter to have autoCreate create folders in > parts, as is done when a permission is set? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21282) camel-file: allow creating folders one by one
[ https://issues.apache.org/jira/browse/CAMEL-21282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885270#comment-17885270 ] Sven edited comment on CAMEL-21282 at 9/27/24 8:32 AM: --- Well in our case yes because we can't use SMB in Azure on container apps, but this doesn't negate the fact that camel-file using Azure file share SMB is not isofunctional with using other SMB file shares (due to a restriction on Azure Files). MS already indicated they have no intention of resolving this limitation.. was (Author: JIRAUSER302579): Well in our case yes because we can't use SMB in Azure on containers, but this doesn't negate the fact that camel-file using Azure file share SMB is not isofunctional with using other SMB file shares (due to a restriction on Azure Files). MS already indicated they have no intention of resolving this limitation.. > camel-file: allow creating folders one by one > - > > Key: CAMEL-21282 > URL: https://issues.apache.org/jira/browse/CAMEL-21282 > Project: Camel > Issue Type: Wish > Components: camel-file >Affects Versions: 4.8.0 >Reporter: Sven >Priority: Major > Attachments: image-2024-09-26-17-58-10-424.png > > > We are using camel-file to write to an Azure File Share, but this fails > sometimes because our routes can create files in nested folders. > This works fine for a Windows share but Azure shares apparently don't support > creating multiple folders at once. > The code shows it only does this iteratively if there are permissions set but > the file share doesn't support Posix (we're running in Windows), setting > permissions throws an UnsupportedOperationException. > From org.apache.camel.component.file.FileOperations: > !image-2024-09-26-17-58-10-424.png|width=771,height=308! > > would it be possible to add a parameter to have autoCreate create folders in > parts, as is done when a permission is set? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21279) camel-jbang - Export using custom kamelets should not add not needed kamelet JARs
[ https://issues.apache.org/jira/browse/CAMEL-21279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885091#comment-17885091 ] Claus Ibsen edited comment on CAMEL-21279 at 9/27/24 8:41 AM: -- TODO: exporting with custom kamelets in same folder, should be moved into kamelets folder. *DONE* TODO: kamelets is created as a file and not dir *DONE* TODO: camel-kamelet in pom.xml TODO: remove camel-kamelets-catalog in pom.xml TODO: only include camel-kamelets if using any of the ASF kamelets was (Author: davsclaus): TODO: exporting with custom kamelets in same folder, should be moved into kamelets folder. TODO: kamelets is created as a file and not dir *DONE* TODO: camel-kamelet in pom.xml TODO: remove camel-kamelets-catalog in pom.xml TODO: only include camel-kamelets if using any of the ASF kamelets > camel-jbang - Export using custom kamelets should not add not needed kamelet > JARs > - > > Key: CAMEL-21279 > URL: https://issues.apache.org/jira/browse/CAMEL-21279 > Project: Camel > Issue Type: Improvement > Components: camel-jbang >Affects Versions: 4.8.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.8.1, 4.9.0 > > > There seems to be that camel-kamelets-catalog and camel-kamelets-util JARs > are added even if they are not in use due to using custom kamelets. > We should trim down. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21285) [camel-jbang] Error exporting from different directory
[
https://issues.apache.org/jira/browse/CAMEL-21285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885341#comment-17885341
]
Pasquale Congiusti commented on CAMEL-21285:
I see. The problem is that I was developing some test to verify that the
exported content has all the expected output. You cannot test without recurring
to an "external" path from Junit. I will try to see how we can have a simple
generic approach without adding more complexity to the actual implementation.
> [camel-jbang] Error exporting from different directory
> ---
>
> Key: CAMEL-21285
> URL: https://issues.apache.org/jira/browse/CAMEL-21285
> Project: Camel
> Issue Type: Bug
>Affects Versions: 4.9.0
>Reporter: Pasquale Congiusti
>Assignee: Pasquale Congiusti
>Priority: Minor
> Fix For: 4.9.0
>
>
> While working on some strengthening export test to validate the output I
> bumped into this bug:
> {code}
> camel export tmp/test.yaml --runtime quarkus --gav o:a:1.0.0 --dir ceq
> {code}
> would produce a wrong export as it correctly set the route into
> src/main/resources/camel but it wrongly set the application.properties with
> camel.main.routes-include-pattern=camel/tmp/test.yaml
> The result is an application that fails to execute.
> The same problem happens with Java which are distributed to a different
> folder and a different application properties configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-21286) Add a cache to JAXB object factories on JAXB Marshalling/Fallback converter
Adriano Machado created CAMEL-21286: --- Summary: Add a cache to JAXB object factories on JAXB Marshalling/Fallback converter Key: CAMEL-21286 URL: https://issues.apache.org/jira/browse/CAMEL-21286 Project: Camel Issue Type: Improvement Components: camel-jaxb Affects Versions: 4.4.3 Reporter: Adriano Machado Camel is calling `JaxbHelper.getJaxbElementFactoryMethod` and the result is not being cached. This expensive call on apps with schemas deployed on nested jars on Spring Boot apps running on Openshift. -- This message was sent by Atlassian Jira (v8.20.10#820010)
