[jira] [Commented] (CAMEL-7469) Make CamelBlueprintTestSupport tests more predictable
[
https://issues.apache.org/jira/browse/CAMEL-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884209#comment-16884209
]
Jan Bednar commented on CAMEL-7469:
---
Hello [~arun12376]. Camel 2.17 is EOL and no more fixes will be released on
2.17 branch. You can try to find some help on
[https://camel.apache.org/mailing-lists.html] or
[https://stackoverflow.com|https://stackoverflow.com/]. Please post concrete
problem with all relevant details, instead of "me too" as you did in this
comment.
> Make CamelBlueprintTestSupport tests more predictable
> -
>
> Key: CAMEL-7469
> URL: https://issues.apache.org/jira/browse/CAMEL-7469
> Project: Camel
> Issue Type: Improvement
> Components: camel-blueprint
>Affects Versions: 2.13.1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 2.12.4, 2.13.2, 2.14.0
>
>
> Currently the tests which override
> {{org.apache.camel.test.blueprint.CamelBlueprintTestSupport#useOverridePropertiesWithConfigAdmin}}
> or
> {{org.apache.camel.test.blueprint.CamelBlueprintTestSupport#loadConfigAdminConfigurationFile}}
> have race issue, because changing configuration leads to reload of Blueprint
> Container.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (CAMEL-7469) Make CamelBlueprintTestSupport tests more predictable
[
https://issues.apache.org/jira/browse/CAMEL-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884146#comment-16884146
]
Arun Kumar commented on CAMEL-7469:
---
I am using camel 2.17.0 but still having below error while running Junit using
CamelBlueprintTestSupport even not overriding any config method.
"java.lang.RuntimeException: Gave up waiting for service
(objectClass=org.apache.camel.CamelContext)"
> Make CamelBlueprintTestSupport tests more predictable
> -
>
> Key: CAMEL-7469
> URL: https://issues.apache.org/jira/browse/CAMEL-7469
> Project: Camel
> Issue Type: Improvement
> Components: camel-blueprint
>Affects Versions: 2.13.1
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>Priority: Major
> Fix For: 2.12.4, 2.13.2, 2.14.0
>
>
> Currently the tests which override
> {{org.apache.camel.test.blueprint.CamelBlueprintTestSupport#useOverridePropertiesWithConfigAdmin}}
> or
> {{org.apache.camel.test.blueprint.CamelBlueprintTestSupport#loadConfigAdminConfigurationFile}}
> have race issue, because changing configuration leads to reload of Blueprint
> Container.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (CAMEL-13424) Rest Component custom routeId is not accessible in processor
[
https://issues.apache.org/jira/browse/CAMEL-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Freeman Fang resolved CAMEL-13424.
--
Resolution: Fixed
Fix Version/s: 3.0.0.M5
2.25.0
2.24.2
2.23.4
3.0.0
> Rest Component custom routeId is not accessible in processor
>
>
> Key: CAMEL-13424
> URL: https://issues.apache.org/jira/browse/CAMEL-13424
> Project: Camel
> Issue Type: Bug
> Components: came-core, rest
>Affects Versions: 2.23.1
> Environment: Apache camel 2.23.x,Tomcat 9, JDK 8
>Reporter: Maheswara Prasanna Govindasamy
>Assignee: Freeman Fang
>Priority: Major
> Fix For: 3.0.0, 2.23.4, 2.24.2, 2.25.0, 3.0.0.M5
>
> Attachments: Camel13424Test.java
>
>
> Rest component route id set in routebuilder is not accessible in processor.
> Below is the example
> RouteBuilder:
> {{rest("/app").get("/test").id("REST-TEST").to("direct:test").endRest();}}
> from("direct:test").routeId("TEST").id("TEST").process("TestProcessor");
> or
> rest("/app").get("/test").route().routeId("TEST").id("REST-TEST")
> {{Processor:}}
> {{String routeId = exchange.getFromRouteId();}}{{}}
> {{routeId is always random id in case of apache camel 2.23.x but works in
> 2.22.x versions.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (CAMEL-13424) Rest Component custom routeId is not accessible in processor
[
https://issues.apache.org/jira/browse/CAMEL-13424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16884120#comment-16884120
]
Freeman Fang commented on CAMEL-13424:
--
test case added in camel code base to ensure it works
> Rest Component custom routeId is not accessible in processor
>
>
> Key: CAMEL-13424
> URL: https://issues.apache.org/jira/browse/CAMEL-13424
> Project: Camel
> Issue Type: Bug
> Components: came-core, rest
>Affects Versions: 2.23.1
> Environment: Apache camel 2.23.x,Tomcat 9, JDK 8
>Reporter: Maheswara Prasanna Govindasamy
>Assignee: Freeman Fang
>Priority: Major
> Attachments: Camel13424Test.java
>
>
> Rest component route id set in routebuilder is not accessible in processor.
> Below is the example
> RouteBuilder:
> {{rest("/app").get("/test").id("REST-TEST").to("direct:test").endRest();}}
> from("direct:test").routeId("TEST").id("TEST").process("TestProcessor");
> or
> rest("/app").get("/test").route().routeId("TEST").id("REST-TEST")
> {{Processor:}}
> {{String routeId = exchange.getFromRouteId();}}{{}}
> {{routeId is always random id in case of apache camel 2.23.x but works in
> 2.22.x versions.}}
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (CAMEL-13741) Map to Iterable converter regression
[
https://issues.apache.org/jira/browse/CAMEL-13741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16883803#comment-16883803
]
Andrea Cosentino commented on CAMEL-13741:
--
I didn't merge the 2.x stuff, because I noticed the failures. I'm going to
close the PR for 2.x and we are waiting for your contributiosn next week.
Thanks for your time.
> Map to Iterable converter regression
>
>
> Key: CAMEL-13741
> URL: https://issues.apache.org/jira/browse/CAMEL-13741
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Affects Versions: 2.20.0
>Reporter: Antoine DESSAIGNE
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When converting a {{Map}} to an {{Iterable}} the results is no longer the
> same since CAMEL-11379.
> Given the following context
> {code}
>
> http://camel.apache.org/schema/spring;>
>
>
>
> [A: 'aa', B: 'bb', C: 'cc', D: 'dd']
>
>
>
> ${body}
>
>
>
>
> {code}
> It produces 4 log messages in camel 2.18.3 using the converter
> {{CollectionConverter.toSet(java.util.Map)}}. Using camel 2.24.1 it
> produces only one message containing the whole list. This is due to
> {{ObjectConverterOptimised}} calling
> {{ObjectHelper.createIterable(java.lang.Object)}} which has a fallback to
> {{Collections.singletonList(value)}} thus producing a single entry with the
> whole Map.
> The fix is probably to add in
> {{ObjectHelper.createIterable(java.lang.Object)}} the following code
> {code}
> if (value instanceof Map) {
> return ((Map)value).entrySet();
> }
> {code}
> but I would like to know what you think about it before doing a pull request.
> Thanks
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (CAMEL-13741) Map to Iterable converter regression
[
https://issues.apache.org/jira/browse/CAMEL-13741?focusedWorklogId=275911=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-275911
]
ASF GitHub Bot logged work on CAMEL-13741:
--
Author: ASF GitHub Bot
Created on: 12/Jul/19 13:22
Start Date: 12/Jul/19 13:22
Worklog Time Spent: 10m
Work Description: oscerd commented on pull request #3035: CAMEL-13741 -
Allow to convert a Map to an Iterable
URL: https://github.com/apache/camel/pull/3035
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 275911)
Time Spent: 0.5h (was: 20m)
> Map to Iterable converter regression
>
>
> Key: CAMEL-13741
> URL: https://issues.apache.org/jira/browse/CAMEL-13741
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Affects Versions: 2.20.0
>Reporter: Antoine DESSAIGNE
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When converting a {{Map}} to an {{Iterable}} the results is no longer the
> same since CAMEL-11379.
> Given the following context
> {code}
>
> http://camel.apache.org/schema/spring;>
>
>
>
> [A: 'aa', B: 'bb', C: 'cc', D: 'dd']
>
>
>
> ${body}
>
>
>
>
> {code}
> It produces 4 log messages in camel 2.18.3 using the converter
> {{CollectionConverter.toSet(java.util.Map)}}. Using camel 2.24.1 it
> produces only one message containing the whole list. This is due to
> {{ObjectConverterOptimised}} calling
> {{ObjectHelper.createIterable(java.lang.Object)}} which has a fallback to
> {{Collections.singletonList(value)}} thus producing a single entry with the
> whole Map.
> The fix is probably to add in
> {{ObjectHelper.createIterable(java.lang.Object)}} the following code
> {code}
> if (value instanceof Map) {
> return ((Map)value).entrySet();
> }
> {code}
> but I would like to know what you think about it before doing a pull request.
> Thanks
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (CAMEL-13741) Map to Iterable converter regression
[
https://issues.apache.org/jira/browse/CAMEL-13741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16883762#comment-16883762
]
Andrea Cosentino commented on CAMEL-13741:
--
I reverted on master, we need to review a bunch of CSV tests first.
[~antoine.dessaigne] please can you have a look? Thanks.
> Map to Iterable converter regression
>
>
> Key: CAMEL-13741
> URL: https://issues.apache.org/jira/browse/CAMEL-13741
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Affects Versions: 2.20.0
>Reporter: Antoine DESSAIGNE
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When converting a {{Map}} to an {{Iterable}} the results is no longer the
> same since CAMEL-11379.
> Given the following context
> {code}
>
> http://camel.apache.org/schema/spring;>
>
>
>
> [A: 'aa', B: 'bb', C: 'cc', D: 'dd']
>
>
>
> ${body}
>
>
>
>
> {code}
> It produces 4 log messages in camel 2.18.3 using the converter
> {{CollectionConverter.toSet(java.util.Map)}}. Using camel 2.24.1 it
> produces only one message containing the whole list. This is due to
> {{ObjectConverterOptimised}} calling
> {{ObjectHelper.createIterable(java.lang.Object)}} which has a fallback to
> {{Collections.singletonList(value)}} thus producing a single entry with the
> whole Map.
> The fix is probably to add in
> {{ObjectHelper.createIterable(java.lang.Object)}} the following code
> {code}
> if (value instanceof Map) {
> return ((Map)value).entrySet();
> }
> {code}
> but I would like to know what you think about it before doing a pull request.
> Thanks
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Comment Edited] (CAMEL-13454) camel-testcontainers - Should build if no docker
[
https://issues.apache.org/jira/browse/CAMEL-13454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16883745#comment-16883745
]
Alexandros Koufoudakis edited comment on CAMEL-13454 at 7/12/19 12:04 PM:
--
Another update. The only way (until now) I was able to make it working on
Mojave, was the following:
testcontainers-skip-tests
!integration-test
maven-surefire-plugin
true
maven-failsafe-plugin
true
[~davsclaus] can you, please, check whether it works for you on your macOS?
If it works, what should we do next?
was (Author: akoufoudakis):
Another update. The only way (until now) I was able to make it working on
Mojave, was the following:
{{}}
{{ testcontainers-skip-tests}}
{{ }}
{{ }}
{{ !integration-test}}
{{ }}
{{ }}
{{ }}
{{ }}
{{ }}
{{ maven-surefire-plugin}}
{{ }}
{{ true}}
{{ }}
{{ }}
{{ }}
{{ maven-failsafe-plugin}}
{{ }}
{{ true}}
{{ }}
{{ }}
{{ }}
{{ }}
{{}}
[~davsclaus] can you, please, check whether it works for you on your macOS?
If it works, what should we do next?
> camel-testcontainers - Should build if no docker
>
>
> Key: CAMEL-13454
> URL: https://issues.apache.org/jira/browse/CAMEL-13454
> Project: Camel
> Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Ramu
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: pom.xml
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If you run mvn clean install then the following should still pass.
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running
> org.apache.camel.test.testcontainers.ContainerAwareTestSupportIT
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 31.178 s <<< FAILURE! - in
> org.apache.camel.test.testcontainers.ContainerAwareTestSupportIT
> [ERROR]
> testPropertyPlaceholders(org.apache.camel.test.testcontainers.ContainerAwareTestSupportIT)
> Time elapsed: 30.805 s <<< ERROR!
> java.lang.IllegalStateException: Could not find a valid Docker environment.
> Please see logs and check configuration
> at
> org.apache.camel.test.testcontainers.ContainerAwareTestSupportIT.createContainer(ContainerAwareTestSupportIT.java:37)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR]
> ContainerAwareTestSupportIT>CamelTestSupport.setUp:284->ContainerAwareTestSupport.setupResources:42->ContainerAwareTestSupport.createContainers:76->createContainer:37
> » IllegalState
> [INFO]
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> [INFO]
> [INFO]
> [INFO] --- maven-failsafe-plugin:2.22.1:verify (default) @
> camel-testcontainers ---
> [INFO]
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (CAMEL-13454) camel-testcontainers - Should build if no docker
[
https://issues.apache.org/jira/browse/CAMEL-13454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16883745#comment-16883745
]
Alexandros Koufoudakis commented on CAMEL-13454:
Another update. The only way (until now) I was able to make it working on
Mojave, was the following:
{{}}
{{ testcontainers-skip-tests}}
{{ }}
{{ }}
{{ !integration-test}}
{{ }}
{{ }}
{{ }}
{{ }}
{{ }}
{{ maven-surefire-plugin}}
{{ }}
{{ true}}
{{ }}
{{ }}
{{ }}
{{ maven-failsafe-plugin}}
{{ }}
{{ true}}
{{ }}
{{ }}
{{ }}
{{ }}
{{}}
[~davsclaus] can you, please, check whether it works for you on your macOS?
If it works, what should we do next?
> camel-testcontainers - Should build if no docker
>
>
> Key: CAMEL-13454
> URL: https://issues.apache.org/jira/browse/CAMEL-13454
> Project: Camel
> Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Ramu
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: pom.xml
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If you run mvn clean install then the following should still pass.
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running
> org.apache.camel.test.testcontainers.ContainerAwareTestSupportIT
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 31.178 s <<< FAILURE! - in
> org.apache.camel.test.testcontainers.ContainerAwareTestSupportIT
> [ERROR]
> testPropertyPlaceholders(org.apache.camel.test.testcontainers.ContainerAwareTestSupportIT)
> Time elapsed: 30.805 s <<< ERROR!
> java.lang.IllegalStateException: Could not find a valid Docker environment.
> Please see logs and check configuration
> at
> org.apache.camel.test.testcontainers.ContainerAwareTestSupportIT.createContainer(ContainerAwareTestSupportIT.java:37)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR]
> ContainerAwareTestSupportIT>CamelTestSupport.setUp:284->ContainerAwareTestSupport.setupResources:42->ContainerAwareTestSupport.createContainers:76->createContainer:37
> » IllegalState
> [INFO]
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> [INFO]
> [INFO]
> [INFO] --- maven-failsafe-plugin:2.22.1:verify (default) @
> camel-testcontainers ---
> [INFO]
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (CAMEL-13733) camel-cloud - depend on camel-core-engine
[ https://issues.apache.org/jira/browse/CAMEL-13733?focusedWorklogId=275832=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-275832 ] ASF GitHub Bot logged work on CAMEL-13733: -- Author: ASF GitHub Bot Created on: 12/Jul/19 11:24 Start Date: 12/Jul/19 11:24 Worklog Time Spent: 10m Work Description: onderson commented on pull request #3039: CAMEL-13733-update pom.xml to use camel-core-engin URL: https://github.com/apache/camel/pull/3039 ...e 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 275832) Time Spent: 10m Remaining Estimate: 0h > camel-cloud - depend on camel-core-engine > - > > Key: CAMEL-13733 > URL: https://issues.apache.org/jira/browse/CAMEL-13733 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (CAMEL-13748) Create Spring Boot integration test for camel-file-watch component
Jan Bednar created CAMEL-13748: -- Summary: Create Spring Boot integration test for camel-file-watch component Key: CAMEL-13748 URL: https://issues.apache.org/jira/browse/CAMEL-13748 Project: Camel Issue Type: Task Reporter: Jan Bednar Assignee: Jan Bednar -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (CAMEL-13628) Implement camel-file-watch component
[ https://issues.apache.org/jira/browse/CAMEL-13628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino reassigned CAMEL-13628: Assignee: Jan Bednar > Implement camel-file-watch component > > > Key: CAMEL-13628 > URL: https://issues.apache.org/jira/browse/CAMEL-13628 > Project: Camel > Issue Type: New Feature >Reporter: Jan Bednar >Assignee: Jan Bednar >Priority: Minor > Fix For: 3.0.0, 3.0.0.M5 > > Time Spent: 20m > Remaining Estimate: 0h > > As discussed on mailing list. > [http://camel.465427.n5.nabble.com/New-component-PoC-Watch-modifications-in-directory-td5835854.html] > This component will be consumer-only. > Features: > * Watch events (File added, File removed, File modified) in directory > * Allow to watch directory and subdirectories (recursive) > * Allow filtering by event types > * Support filtering of events using SImple File language > * Use queue for consumed events (WatchService does not handle well slow > consumers and OVERFLOW occurs). Support option concurrentConsumers and size > * Type converters (Event -> CamelFile) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-13628) Implement camel-file-watch component
[ https://issues.apache.org/jira/browse/CAMEL-13628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-13628. -- Resolution: Fixed > Implement camel-file-watch component > > > Key: CAMEL-13628 > URL: https://issues.apache.org/jira/browse/CAMEL-13628 > Project: Camel > Issue Type: New Feature >Reporter: Jan Bednar >Assignee: Jan Bednar >Priority: Minor > Fix For: 3.0.0, 3.0.0.M5 > > Time Spent: 20m > Remaining Estimate: 0h > > As discussed on mailing list. > [http://camel.465427.n5.nabble.com/New-component-PoC-Watch-modifications-in-directory-td5835854.html] > This component will be consumer-only. > Features: > * Watch events (File added, File removed, File modified) in directory > * Allow to watch directory and subdirectories (recursive) > * Allow filtering by event types > * Support filtering of events using SImple File language > * Use queue for consumed events (WatchService does not handle well slow > consumers and OVERFLOW occurs). Support option concurrentConsumers and size > * Type converters (Event -> CamelFile) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Work logged] (CAMEL-13628) Implement camel-file-watch component
[ https://issues.apache.org/jira/browse/CAMEL-13628?focusedWorklogId=275792=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-275792 ] ASF GitHub Bot logged work on CAMEL-13628: -- Author: ASF GitHub Bot Created on: 12/Jul/19 10:49 Start Date: 12/Jul/19 10:49 Worklog Time Spent: 10m Work Description: oscerd commented on pull request #3019: CAMEL-13628: Implemented file-watch component URL: https://github.com/apache/camel/pull/3019 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 275792) Time Spent: 20m (was: 10m) > Implement camel-file-watch component > > > Key: CAMEL-13628 > URL: https://issues.apache.org/jira/browse/CAMEL-13628 > Project: Camel > Issue Type: New Feature >Reporter: Jan Bednar >Priority: Minor > Fix For: 3.0.0, 3.0.0.M5 > > Time Spent: 20m > Remaining Estimate: 0h > > As discussed on mailing list. > [http://camel.465427.n5.nabble.com/New-component-PoC-Watch-modifications-in-directory-td5835854.html] > This component will be consumer-only. > Features: > * Watch events (File added, File removed, File modified) in directory > * Allow to watch directory and subdirectories (recursive) > * Allow filtering by event types > * Support filtering of events using SImple File language > * Use queue for consumed events (WatchService does not handle well slow > consumers and OVERFLOW occurs). Support option concurrentConsumers and size > * Type converters (Event -> CamelFile) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (CAMEL-13628) Implement camel-file-watch component
[ https://issues.apache.org/jira/browse/CAMEL-13628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-13628: - Fix Version/s: 3.0.0.M5 3.0.0 > Implement camel-file-watch component > > > Key: CAMEL-13628 > URL: https://issues.apache.org/jira/browse/CAMEL-13628 > Project: Camel > Issue Type: New Feature >Reporter: Jan Bednar >Priority: Minor > Fix For: 3.0.0, 3.0.0.M5 > > Time Spent: 20m > Remaining Estimate: 0h > > As discussed on mailing list. > [http://camel.465427.n5.nabble.com/New-component-PoC-Watch-modifications-in-directory-td5835854.html] > This component will be consumer-only. > Features: > * Watch events (File added, File removed, File modified) in directory > * Allow to watch directory and subdirectories (recursive) > * Allow filtering by event types > * Support filtering of events using SImple File language > * Use queue for consumed events (WatchService does not handle well slow > consumers and OVERFLOW occurs). Support option concurrentConsumers and size > * Type converters (Event -> CamelFile) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-11502) Cleanup .htaccess
[ https://issues.apache.org/jira/browse/CAMEL-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-11502. --- Resolution: Fixed Fix Version/s: 3.0.0.M5 > Cleanup .htaccess > - > > Key: CAMEL-11502 > URL: https://issues.apache.org/jira/browse/CAMEL-11502 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.0.0.M5 > > > Current .htaccess is from HTML5 Boilerplate project, it should be cleaned to > contain only the necessary configuration. Also check with ASF if there are > any restrictions on .htaccess file. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (CAMEL-11502) Cleanup .htaccess
[ https://issues.apache.org/jira/browse/CAMEL-11502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart reassigned CAMEL-11502: - Assignee: Zoran Regvart > Cleanup .htaccess > - > > Key: CAMEL-11502 > URL: https://issues.apache.org/jira/browse/CAMEL-11502 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Assignee: Zoran Regvart >Priority: Major > Labels: help-wanted > > Current .htaccess is from HTML5 Boilerplate project, it should be cleaned to > contain only the necessary configuration. Also check with ASF if there are > any restrictions on .htaccess file. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (CAMEL-13629) Some tests are excluded from maven build because of wrong class name
[
https://issues.apache.org/jira/browse/CAMEL-13629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-13629.
--
Resolution: Fixed
> Some tests are excluded from maven build because of wrong class name
>
>
> Key: CAMEL-13629
> URL: https://issues.apache.org/jira/browse/CAMEL-13629
> Project: Camel
> Issue Type: Test
>Reporter: Jan Bednar
>Assignee: Jan Bednar
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M5
>
> Attachments: grepResult.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There are some tests, which were probably meant to run during build, but does
> not follow .*Test.java or *IT.java filename pattern.
>
> This returns 46 files on current master (output attached):
> {code:java}
> grep -rnw './camel' --include=\*.java -e '@Test' -l | grep -v -e
> '.*Test.java' -e '.*TestSupport.java' -e '.*TestBase.java' -e '.*IT.java'
> {code}
> This method is not bulletproof and returns some false-positives, but most of
> the matches should be IMO renamed to follow filename patternt and thus be
> executed during maven build.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (CAMEL-13629) Some tests are excluded from maven build because of wrong class name
[
https://issues.apache.org/jira/browse/CAMEL-13629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-13629:
-
Fix Version/s: 3.0.0.M5
3.0.0
> Some tests are excluded from maven build because of wrong class name
>
>
> Key: CAMEL-13629
> URL: https://issues.apache.org/jira/browse/CAMEL-13629
> Project: Camel
> Issue Type: Test
>Reporter: Jan Bednar
>Assignee: Jan Bednar
>Priority: Minor
> Fix For: 3.0.0, 3.0.0.M5
>
> Attachments: grepResult.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There are some tests, which were probably meant to run during build, but does
> not follow .*Test.java or *IT.java filename pattern.
>
> This returns 46 files on current master (output attached):
> {code:java}
> grep -rnw './camel' --include=\*.java -e '@Test' -l | grep -v -e
> '.*Test.java' -e '.*TestSupport.java' -e '.*TestBase.java' -e '.*IT.java'
> {code}
> This method is not bulletproof and returns some false-positives, but most of
> the matches should be IMO renamed to follow filename patternt and thus be
> executed during maven build.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Work logged] (CAMEL-13629) Some tests are excluded from maven build because of wrong class name
[
https://issues.apache.org/jira/browse/CAMEL-13629?focusedWorklogId=275740=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-275740
]
ASF GitHub Bot logged work on CAMEL-13629:
--
Author: ASF GitHub Bot
Created on: 12/Jul/19 09:39
Start Date: 12/Jul/19 09:39
Worklog Time Spent: 10m
Work Description: oscerd commented on pull request #3036: CAMEL-13629:
Renamed tests to follow *Test pattern
URL: https://github.com/apache/camel/pull/3036
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
---
Worklog Id: (was: 275740)
Time Spent: 20m (was: 10m)
> Some tests are excluded from maven build because of wrong class name
>
>
> Key: CAMEL-13629
> URL: https://issues.apache.org/jira/browse/CAMEL-13629
> Project: Camel
> Issue Type: Test
>Reporter: Jan Bednar
>Assignee: Jan Bednar
>Priority: Minor
> Attachments: grepResult.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> There are some tests, which were probably meant to run during build, but does
> not follow .*Test.java or *IT.java filename pattern.
>
> This returns 46 files on current master (output attached):
> {code:java}
> grep -rnw './camel' --include=\*.java -e '@Test' -l | grep -v -e
> '.*Test.java' -e '.*TestSupport.java' -e '.*TestBase.java' -e '.*IT.java'
> {code}
> This method is not bulletproof and returns some false-positives, but most of
> the matches should be IMO renamed to follow filename patternt and thus be
> executed during maven build.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Resolved] (CAMEL-13746) camel-salesforce integration tests deserialization issue
[ https://issues.apache.org/jira/browse/CAMEL-13746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Dettinger resolved CAMEL-13746. Resolution: Fixed > camel-salesforce integration tests deserialization issue > > > Key: CAMEL-13746 > URL: https://issues.apache.org/jira/browse/CAMEL-13746 > Project: Camel > Issue Type: Bug > Components: camel-salesforce >Affects Versions: 3.0.0-M3 >Reporter: Alex Dettinger >Assignee: Alex Dettinger >Priority: Major > Fix For: 3.0.0.M5 > > > Multiple fix/enhancements are need: > + The JobInfo de-serialization is not working anymore (no more namespace > aware) > + itests are also executed during test phase > + few typos in documentation > + some tests are not designed to run in concurrency with others -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Work logged] (CAMEL-13747) Adding basic auth support to camel-solr
[ https://issues.apache.org/jira/browse/CAMEL-13747?focusedWorklogId=275672=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-275672 ] ASF GitHub Bot logged work on CAMEL-13747: -- Author: ASF GitHub Bot Created on: 12/Jul/19 06:40 Start Date: 12/Jul/19 06:40 Worklog Time Spent: 10m Work Description: renjfk commented on pull request #3038: CAMEL-13747: Added basic auth support to camel-solr URL: https://github.com/apache/camel/pull/3038 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 275672) Time Spent: 10m Remaining Estimate: 0h > Adding basic auth support to camel-solr > --- > > Key: CAMEL-13747 > URL: https://issues.apache.org/jira/browse/CAMEL-13747 > Project: Camel > Issue Type: Improvement > Components: camel-solr >Reporter: Soner Koksal >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Adding basic auth support to camel-solr according to instructions stated > [here|https://lucene.apache.org/solr/guide/7_7/basic-authentication-plugin.html#using-basic-auth-with-solrj] -- This message was sent by Atlassian JIRA (v7.6.14#76016)
