building camel code (init eclipse workspace)
Hello, i am trying to build source code (master - 8 sept 2016) from this page: http://camel.apache.org/building.html i would use eclipse (neon) so i execute this command: mvn -Psetup.eclipse -Declipse.workspace.dir=/path/to/your/workspace zZzzZZzzz after 15 minutes this is the output [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 02:34 min [INFO] Finished at: 2016-09-08T23:07:29+02:00 [INFO] Final Memory: 1034M/2886M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-eclipse-plugin:2.10:eclipse (setup.eclipse.project) on project camel-test-karaf: Unable to resolve resource location: /camel-eclipse-checkstyle -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :camel-test-karaf Can you help me? King regards -- View this message in context: http://camel.465427.n5.nabble.com/building-camel-code-init-eclipse-workspace-tp5787394.html Sent from the Camel Development mailing list archive at Nabble.com.
Re: building camel code (init eclipse workspace)
Thanks a lot claus!!! -- View this message in context: http://camel.465427.n5.nabble.com/building-camel-code-init-eclipse-workspace-tp5787394p5787425.html Sent from the Camel Development mailing list archive at Nabble.com.
[GitHub] camel pull request #1165: fix documentation (map section)
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1165 fix documentation (map section) https://issues.apache.org/jira/browse/CAMEL-10295 Kings regards fabryprog You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-10295 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1165.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1165 commit 6e4fa3d8df3bd520e86359adc579da388d1680a2 Author: Fabryprog Date: 2016-09-10T14:03:51Z fix documentation (map section) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1166: fix bean reference (test)
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1166 fix bean reference (test) Updating hazelcast. There are some test failure, Can you help me? You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-10306 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1166.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1166 commit 88345291b3e8744acf10d1eb95132a3762558a9c Author: Fabryprog Date: 2016-09-10T23:31:21Z fix bean reference (test) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1165: fix documentation (map section)
Github user Fabryprog closed the pull request at: https://github.com/apache/camel/pull/1165 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1166: CAMEL-10306: Upgrade from 3.6.5 to 3.7.1
Github user Fabryprog closed the pull request at: https://github.com/apache/camel/pull/1166 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Camel-docker upgrade library, test failure!
Hello, i am working to this jira https://issues.apache.org/jira/browse/CAMEL-10307 Source code is here: https://github.com/Fabryprog/camel/tree/CAMEL-10307 when i Running tests i have follow error that it could be a JARs conflict. Can you help me? 2016-09-13 15:54:48,426 [main ] INFO AuthCmdHeaderTest - Testing: null(org.apache.camel.component.docker.headers.AuthCmdHeaderTest) 2016-09-13 15:54:48,427 [main ] INFO AuthCmdHeaderTest - 2016-09-13 15:54:49,092 [main ] INFO DefaultCamelContext - Apache Camel 2.18.0-SNAPSHOT (CamelContext: camel-1) is starting 2016-09-13 15:54:49,094 [main ] INFO DefaultManagementStrategy - JMX is disabled 2016-09-13 15:54:49,148 [main ] INFO DefaultTypeConverter - Loaded 189 type converters 2016-09-13 15:54:49,216 [main ] INFO DefaultCamelContext - StreamCaching is not in use. If using streams then its recommended to enable stream caching. See more details at http://camel.apache.org/stream-caching.html 2016-09-13 15:54:49,224 [main ] INFO DefaultCamelContext - Route: route1 started and consuming from: direct://in 2016-09-13 15:54:49,224 [main ] INFO DefaultCamelContext - Total 1 routes, of which 1 are started. 2016-09-13 15:54:49,225 [main ] INFO DefaultCamelContext - Apache Camel 2.18.0-SNAPSHOT (CamelContext: camel-1) started in 0.132 seconds 2016-09-13 15:54:49,271 [main ] INFO DockerClientFactory - Docker clientProfile DockerClientProfile [host=localhost, port=5000, username=jdoe, password=password, email=j...@example.com, serverAddress=http://docker.io/v1, requestTimeout=null, certPath=null, maxTotalConnections=100, maxPerRouteConnections=100, loggingFilterEnabled=false, followRedirectFilterEnabled=false, tlsVerify=false, socket=true] 2016-09-13 15:54:49,762 [main ] ERROR DefaultErrorHandler - Failed delivery for (MessageId: ID-archimede-ubuntu-42944-1473774888486-0-1 on ExchangeId: ID-archimede-ubuntu-42944-1473774888486-0-2). Exhausted after delivery attempt: 1 caught: java.lang.IllegalStateException: Error creating SSL context (algorithm not supported). Message History --- RouteId ProcessorId Processor Elapsed (ms) [route1] [route1] [direct://in ] [ 506] [route1] [to1 ] [docker://auth ] [ 502] Stacktrace --- java.lang.IllegalStateException: Error creating SSL context (algorithm not supported). at org.glassfish.jersey.SslConfigurator.createSSLContext(SslConfigurator.java:801) ~[?:?] at org.glassfish.jersey.SslConfigurator.getDefaultContext(SslConfigurator.java:301) ~[?:?] at org.glassfish.jersey.SslConfigurator.getDefaultContext(SslConfigurator.java:286) ~[?:?] at org.glassfish.jersey.client.JerseyClient$1.getDefaultSslContext(JerseyClient.java:82) ~[?:?] at org.glassfish.jersey.client.JerseyClient$2.get(JerseyClient.java:222) ~[?:?] at org.glassfish.jersey.client.JerseyClient$2.get(JerseyClient.java:219) ~[?:?] at org.glassfish.jersey.internal.util.collection.Values$LazyUnsafeValueImpl.get(Values.java:425) ~[?:?] -- View this message in context: http://camel.465427.n5.nabble.com/Camel-docker-upgrade-library-test-failure-tp5787511.html Sent from the Camel Development mailing list archive at Nabble.com.
Re: Camel-docker upgrade library, test failure!
This is maven dependency tree OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0 [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Camel :: Docker 2.18.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-dependency-plugin:2.10:tree (default-cli) @ camel-docker --- [INFO] org.apache.camel:camel-docker:jar:2.18.0-SNAPSHOT [INFO] +- org.apache.camel:camel-core:jar:2.18.0-SNAPSHOT:compile [INFO] | \- org.slf4j:slf4j-api:jar:1.7.21:compile [INFO] +- com.github.docker-java:docker-java:jar:3.0.5:compile [INFO] | +- com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider:jar:2.8.2:compile [INFO] | | +- com.fasterxml.jackson.jaxrs:jackson-jaxrs-base:jar:2.8.2:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-core:jar:2.8.2:compile [INFO] | | +- com.fasterxml.jackson.core:jackson-databind:jar:2.8.2:compile [INFO] | | | \- com.fasterxml.jackson.core:jackson-annotations:jar:2.8.2:compile [INFO] | | \- com.fasterxml.jackson.module:jackson-module-jaxb-annotations:jar:2.8.2:compile [INFO] | +- org.glassfish.jersey.connectors:jersey-apache-connector:jar:2.23.1:compile [INFO] | | +- org.glassfish.jersey.core:jersey-common:jar:2.23.1:compile [INFO] | | | +- javax.annotation:javax.annotation-api:jar:1.2:compile [INFO] | | | +- org.glassfish.jersey.bundles.repackaged:jersey-guava:jar:2.23.1:compile [INFO] | | | \- org.glassfish.hk2:osgi-resource-locator:jar:1.0.1:compile [INFO] | | \- javax.ws.rs:javax.ws.rs-api:jar:2.0.1:compile [INFO] | +- org.apache.httpcomponents:httpcore:jar:4.4.4:compile [INFO] | +- org.apache.httpcomponents:httpclient:jar:4.5:compile [INFO] | | \- commons-logging:commons-logging:jar:1.2:compile [INFO] | +- org.glassfish.jersey.core:jersey-client:jar:2.23.1:compile [INFO] | | +- org.glassfish.hk2:hk2-api:jar:2.4.0-b34:compile [INFO] | | | +- org.glassfish.hk2:hk2-utils:jar:2.4.0-b34:compile [INFO] | | | \- org.glassfish.hk2.external:aopalliance-repackaged:jar:2.4.0-b34:compile [INFO] | | +- org.glassfish.hk2.external:javax.inject:jar:2.4.0-b34:compile [INFO] | | \- org.glassfish.hk2:hk2-locator:jar:2.4.0-b34:compile [INFO] | | \- org.javassist:javassist:jar:3.18.1-GA:compile [INFO] | +- de.gesellix:unix-socket-factory:jar:2015-01-27T15-02-14:compile [INFO] | +- org.apache.commons:commons-compress:jar:1.12:compile [INFO] | +- commons-codec:commons-codec:jar:1.10:compile [INFO] | +- commons-lang:commons-lang:jar:2.6:compile [INFO] | +- commons-io:commons-io:jar:2.4:compile [INFO] | +- org.slf4j:jcl-over-slf4j:jar:1.7.21:compile [INFO] | +- com.google.guava:guava:jar:19.0:compile [INFO] | +- org.bouncycastle:bcpkix-jdk15on:jar:1.54:compile [INFO] | | \- org.bouncycastle:bcprov-jdk15on:jar:1.54:compile [INFO] | +- io.netty:netty-codec-http:jar:4.1.3.Final:compile [INFO] | | \- io.netty:netty-codec:jar:4.1.3.Final:compile [INFO] | +- io.netty:netty-handler:jar:4.1.3.Final:compile [INFO] | | +- io.netty:netty-buffer:jar:4.1.3.Final:compile [INFO] | | \- io.netty:netty-transport:jar:4.1.3.Final:compile [INFO] | | \- io.netty:netty-resolver:jar:4.1.3.Final:compile [INFO] | +- io.netty:netty-handler-proxy:jar:4.1.3.Final:compile [INFO] | | \- io.netty:netty-codec-socks:jar:4.1.3.Final:compile [INFO] | \- io.netty:netty-transport-native-epoll:jar:linux-x86_64:4.1.3.Final:compile [INFO] | \- io.netty:netty-common:jar:4.1.3.Final:compile [INFO] +- com.github.jnr:jffi:jar:1.2.7:compile [INFO] +- com.github.jnr:jffi:jar:native:1.2.7:runtime [INFO] +- com.github.jnr:jnr-x86asm:jar:1.0.2:compile [INFO] +- org.apache.logging.log4j:log4j-api:jar:2.6.2:test [INFO] +- org.apache.logging.log4j:log4j-core:jar:2.6.2:test [INFO] +- org.apache.logging.log4j:log4j-slf4j-impl:jar:2.6.2:test [INFO] +- org.apache.camel:camel-test:jar:2.18.0-SNAPSHOT:test [INFO] | \- junit:junit:jar:4.12:test [INFO] | \- org.hamcrest:hamcrest-core:jar:1.3:test [INFO] +- org.powermock:powermock-module-junit4:jar:1.6.1:test [INFO] | \- org.powermock:powermock-module-junit4-common:jar:1.6.1:test [INFO] | +- org.powermock:powermock-core:jar:1.6.1:test [INFO] | \- org.powermock:powermock-reflect:jar:1.6.1:test [INFO] |\- org.objenesis:objenesis:jar:2.1:test [INFO] +- org.powermock:powermock-api-mockito:jar:1.6.1:test [INFO] | +- org.mockito:mockito-all:jar:1.10.8:test [INFO] | \- org.powermock:powermock-api-support:jar:1.6.1:test [INFO] +- org.apache.camel:apt:jar:2.18.0-SNAPSHOT:provided [INFO] | \- org.apache.camel:spi-annotations:jar:2.18.0-SNAPSHOT:provided [INFO] +- org.springframework.boot:spring-boot-configuration-processor:jar:1.4.0.RELEASE:provided [INFO] | +- org.json:json:jar:20140107:provided [INFO] | \- org.springframework:spring-core:jar:4.3.2.RELEASE:provided [INFO
[GitHub] camel pull request #1177: Camel 10319
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1177 Camel 10319 https://issues.apache.org/jira/browse/CAMEL-10319 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-10319 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1177.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1177 commit df323ea0ae5c622e8c0deb391a54d307058a3000 Author: Fabrizio Spataro Date: 2016-09-14T14:09:19Z insert a new SnmpProducer commit fba981f9e19b39ae97560d62dfe7b274ee405b37 Author: Fabrizio Spataro Date: 2016-09-14T14:09:31Z insert a new SnmpProducer commit 5367cae2260724c7d4cc05d433b85e259794dad1 Author: Fabrizio Spataro Date: 2016-09-14T14:25:18Z refactoring + documentation commit d9e46e0cd3a776f0ce0d4d9e6f8dce136f2e9a2e Author: Fabrizio Spataro Date: 2016-09-14T14:33:25Z fix documentation --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Camel-docker upgrade library, test failure!
Hello, this is my branch https://github.com/Fabryprog/camel/tree/CAMEL-10307 -- View this message in context: http://camel.465427.n5.nabble.com/Camel-docker-upgrade-library-test-failure-tp5787511p5787552.html Sent from the Camel Development mailing list archive at Nabble.com.
[GitHub] camel pull request #1177: Camel 10319: SNMP Producer
Github user Fabryprog closed the pull request at: https://github.com/apache/camel/pull/1177 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Camel-docker upgrade library, test failure!
I resolve my problem, it is a simple powermock problem. Resolution is use @PowerMockIgnore annotation!!! -- View this message in context: http://camel.465427.n5.nabble.com/Camel-docker-upgrade-library-test-failure-tp5787511p5787671.html Sent from the Camel Development mailing list archive at Nabble.com.
[GitHub] camel pull request #1180: Camel 10321
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1180 Camel 10321 https://issues.apache.org/jira/browse/CAMEL-10321 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-10321 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1180.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1180 commit 5a198305600d62a88030d9649a1b9b45517e86a6 Author: Fabrizio Spataro Date: 2016-09-15T16:08:23Z CAMEL-10321, camel-asterisk component (without test and doc) commit dad6af0e7333e1566fd573d8a0bd18e7aa318fa3 Author: Fabryprog Date: 2016-09-16T21:25:59Z CAMEL-10321, Asterisk Component: test added commit ff16f2838d29171c8006e6b427acee48b9b7db96 Author: Fabryprog Date: 2016-09-16T22:15:14Z CAMEL-10321, Asterisk Component: documentation adoc commit 9c0d3a1318f3cd88d3abb9f6d35838faa6a7acec Author: Fabryprog Date: 2016-09-16T22:22:46Z CAMEL-10321, Asterisk Component: fix rename class --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1181: Camel 10307: Upgrade docker java version
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1181 Camel 10307: Upgrade docker java version https://issues.apache.org/jira/browse/CAMEL-10307 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-10307 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1181.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1181 commit 9979bbd174669cd431c122c4f5621818c510b9ea Author: Fabrizio Spataro Date: 2016-09-19T16:28:43Z CAMEL-10307, docker library upgrade (async test incomplete) commit b6f521ea16ff4f0f638acb84ab9acfe2a9e88c37 Author: Fabryprog Date: 2016-09-19T22:29:47Z CAMEL-10307, docker test (async) fixed! commit ac7dd5314913a584ee9f1696de3d715bb677e636 Author: Fabrizio Spataro Date: 2016-09-20T08:10:23Z CAMEL-10307, docker lib upgraded! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1181: Camel 10307: Upgrade docker java version
Github user Fabryprog closed the pull request at: https://github.com/apache/camel/pull/1181 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1180: Camel 10321: New Component camel-asterisk
Github user Fabryprog closed the pull request at: https://github.com/apache/camel/pull/1180 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Getting ready for Apache Camel 2.18 Release
Hello,
I may have found a bug derived from 2.18
Before 2.18, i can specified an header like:
[{"firstField": "firstValue",
"secondField":"secondValue"}]
In my bean, *myHeader* will be cast to
*ArrayList>*
After 2.18 upgrade i had an error
*'java.lang.ClassCastException: jdk.nashorn.api.scripting.ScriptObjectMirror
cannot be cast to java.util.List'*
Can you help me? Is it a camel bug or an jdk8 issue?
--
View this message in context:
http://camel.465427.n5.nabble.com/Getting-ready-for-Apache-Camel-2-18-Release-tp5786942p5788108.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: Getting ready for Apache Camel 2.18 Release
for this problem open this issue: https://issues.apache.org/jira/browse/CAMEL-10349 -- View this message in context: http://camel.465427.n5.nabble.com/Getting-ready-for-Apache-Camel-2-18-Release-tp5786942p5788128.html Sent from the Camel Development mailing list archive at Nabble.com.
[GitHub] camel pull request #1189: Camel 10331, Camel Docker Consumer
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1189 Camel 10331, Camel Docker Consumer https://issues.apache.org/jira/browse/CAMEL-10331 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-10331 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1189.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1189 commit f5fa5e1d37d5a6ae8c99dcac3b00408d94f4911a Author: Fabryprog Date: 2016-09-25T14:14:57Z CAMEL-10331, Restore Docker Consumers commit f19e772caa5c27b0ee84f07d7ae06c3f40d3a2d5 Author: Fabryprog Date: 2016-09-25T14:21:05Z CAMEL-10331, fix adoc file --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1189: Camel 10331, Camel Docker Consumer
Github user Fabryprog closed the pull request at: https://github.com/apache/camel/pull/1189 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1190: javaScript setHeader conversion fault
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1190 javaScript setHeader conversion fault https://issues.apache.org/jira/browse/CAMEL-10349 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-10349 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1190.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1190 commit 58b028c3c0572795e92ec17aaae7da75179e183e Author: Fabrizio Spataro Date: 2016-09-28T13:02:39Z CAMEL-10349, insert new test file --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Selector multiple field in header
This is a developer forum. You must ask into this forum: http://camel.465427.n5.nabble.com/Camel-Users-f465428.html -- View this message in context: http://camel.465427.n5.nabble.com/Selector-multiple-field-in-header-tp5788145p5788161.html Sent from the Camel Development mailing list archive at Nabble.com.
Re: New Apache Camel Logo
+1 I have an idea, a logo with a triangle partial and a partial square and a partial rhombus stuck together. It should display the set of components! -- View this message in context: http://camel.465427.n5.nabble.com/New-Apache-Camel-Logo-tp5788206p5788330.html Sent from the Camel Development mailing list archive at Nabble.com.
Re: Need help in camel + restful integration
Hello, this is a wrong forum(developers), you must use camel user forum http://camel.465427.n5.nabble.com/Camel-Users-f465428.html So.. Do you have read this examples? https://github.com/apache/camel/tree/master/examples -- View this message in context: http://camel.465427.n5.nabble.com/Need-help-in-camel-restful-integration-tp5788338p5788340.html Sent from the Camel Development mailing list archive at Nabble.com.
Re: [VOTE] Release Apache Camel 2.18.0
Hello, Into this release when call sqlproducer using CamelSqlQuery i have a new warning log message derived by my body message isn't a JSON object, the component call mongodb type converter. [in my project i have also camel-mongodb component) It is only a warning message + stacktrace, the sql producer work! So I am particularly interested to my PR https://github.com/apache/camel/pull/1190 but anyway my vote is +1!!! PULL out this release and we start working to 2.18.1 release :-) -- View this message in context: http://camel.465427.n5.nabble.com/VOTE-Release-Apache-Camel-2-18-0-tp5788391p5788400.html Sent from the Camel Development mailing list archive at Nabble.com.
camel-extra upgrade 2.18
Hello, More days ago, i sent more PRs into camel-extra project but i haven't any response. Do you known project's owners? thanks! -- View this message in context: http://camel.465427.n5.nabble.com/camel-extra-upgrade-2-18-tp5788435.html Sent from the Camel Development mailing list archive at Nabble.com.
Re: camel-extra upgrade 2.18
Thanks!!! I'll wait, I think the changes are very important -- View this message in context: http://camel.465427.n5.nabble.com/camel-extra-upgrade-2-18-tp5788435p5788550.html Sent from the Camel Development mailing list archive at Nabble.com.
[GitHub] camel pull request #1211: Camel 10327, New Apache drill component
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1211 Camel 10327, New Apache drill component https://issues.apache.org/jira/browse/CAMEL-10327 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-10327 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1211.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1211 commit 59e1110eca2c912f9e4baa30a7d08368be03ebe7 Author: Fabryprog Date: 2016-09-25T21:34:26Z CAMEL-10327, Apache Drill component commit c6444a928797d9aa55002f61362b86d5efaa95e6 Author: Fabrizio Spataro Date: 2016-09-27T06:22:23Z CAMEL-10327, fix doc commit 9e1cc40f0a3a71e2dfa3b21a63ffee380b9773a0 Author: Fabrizio Spataro Date: 2016-10-13T15:03:48Z Merge branch 'master' of https://github.com/Fabryprog/camel into CAMEL-10327 commit 9fb6b99e948747ab934d6e870cae873947f28e2a Author: Fabrizio Spataro Date: 2016-10-14T09:19:33Z CAMEL-10327, new component apache-drill --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1211: Camel 10327, New Apache drill component
Github user Fabryprog closed the pull request at: https://github.com/apache/camel/pull/1211 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1223: Camel 10418, Deploy route with an error
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1223 Camel 10418, Deploy route with an error You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-10418 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1223.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1223 commit 067371d999fefca3614cc9f40b885c5c4d25c767 Author: Fabryprog Date: 2016-10-25T21:19:18Z CAMEL-10418, fix deploy route + test commit 9af2add0a15a88298a427034bb0ea50c00462317 Author: Fabryprog Date: 2016-10-25T21:25:03Z CAMEL-10418, fix deploy route + test commit d8655e47f9fed71af25d86a89f7e36e00981663a Author: Fabryprog Date: 2016-10-25T21:27:16Z CAMEL-10418, fix deploy route + test --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: camel-extra upgrade 2.18
hello to everyone, the open source principle should be clear to everyone. Unfortunately for this project (camel-extra) it seems that the various PR are not important. It seems to have a caste of elect to the throne several days have passed without any response! Can I have some feedback? Thank you -- View this message in context: http://camel.465427.n5.nabble.com/camel-extra-upgrade-2-18-tp5788435p5789293.html Sent from the Camel Development mailing list archive at Nabble.com.
Re: camel-bindy improvements
Hello, Can i have an example? -- View this message in context: http://camel.465427.n5.nabble.com/camel-bindy-improvements-tp5789264p5789308.html Sent from the Camel Development mailing list archive at Nabble.com.
[GitHub] camel pull request #1223: Camel 10418, Deploy route with an error
Github user Fabryprog closed the pull request at: https://github.com/apache/camel/pull/1223 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1331: CAMEL-10560, Gets the file name specified by the c...
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1331 CAMEL-10560, Gets the file name specified by the client https://issues.apache.org/jira/browse/CAMEL-10560 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-10560 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1331.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1331 commit e41bdaaf608b6fc4506f600b5a6a6f5c48a24143 Author: Fabrizio Spataro Date: 2016-12-05T16:42:38Z CAMEL-10560, added getSubmittedFileName() into PartDataSource to retrieve file name specified by the client --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1331: CAMEL-10560, Gets the file name specified by the c...
Github user Fabryprog closed the pull request at: https://github.com/apache/camel/pull/1331 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1339: Camel 10560
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1339 Camel 10560 hello, to able to access new method getSubmittedFileName() (it is not in datasource interface) change class's visibility. Without this fix a cannot access to new method (introduced into servlet 3.x) You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-10560 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1339.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1339 commit e41bdaaf608b6fc4506f600b5a6a6f5c48a24143 Author: Fabrizio Spataro Date: 2016-12-05T16:42:38Z CAMEL-10560, added getSubmittedFileName() into PartDataSource to retrieve file name specified by the client commit 23cf0051b4966a9eea3029b02ae9ceb71755449b Author: Fabrizio Spataro Date: 2016-12-09T11:52:28Z Merge branch 'master' of https://github.com/Fabryprog/camel into CAMEL-10560 commit 4b60f7cbb3f2519deb721b84ffaa3c1dad3ad34d Author: Fabrizio Spataro Date: 2016-12-09T11:52:55Z CAMEL-10560, to able to access new method getSubmittedFileName() (is not in datasource interface) change class's visibility --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Camel Esper (out of camel-extra package)
Hello everybody Into last week i was developing a new version of CamelEsper Component (compatible with latest stable esper version 5.x) but it cannot merge my code into old camel-extra because there are incompatible components inside it (see for example last comment of https://github.com/camel-extra/camel-extra/pull/11) I have a question: Can i fork only camel-esper component and push it into another repo? There are any problem to extract this component from camel-extra package? king regards Fabrizio -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Esper-out-of-camel-extra-package-tp5802466.html Sent from the Camel Development mailing list archive at Nabble.com.
Re: Camel Esper (out of camel-extra package)
Can i have any support? it is a very important issue !!! Today follow components cannot be upgraded: - camel-cics - camel-db4o - camel-esper - camel-exist - camel-firebase - camel-hibernate - camel-jboss - camel-jboss6 - camel-jcifs - camel-rcode - camel-spring-neo4j - camel-virtualbox - camel-vtdxml - camel-wmq - camel-zeromq (https://github.com/camel-extra/camel-extra/tree/master/components) -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Esper-out-of-camel-extra-package-tp5802466p5802780.html Sent from the Camel Development mailing list archive at Nabble.com.
Re: Camel Esper (out of camel-extra package)
Hello claus. i ask again: can i fork camel-esper project and upgrade and push it into another repo? Into an opensource world: nothing is impossible! :-) -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Esper-out-of-camel-extra-package-tp5802466p5802806.html Sent from the Camel Development mailing list archive at Nabble.com.
[GitHub] camel pull request #1870: CAMEL-11631, Camel-Paho Missiong reconnect logic
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1870 CAMEL-11631, Camel-Paho Missiong reconnect logic https://issues.apache.org/jira/browse/CAMEL-11631 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-11631 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1870.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1870 commit f3472922a694473115377e676bd84e39d5e9ba0f Author: Fabrizio Spataro Date: 2017-08-04T12:30:10Z CAMEL-11631, Camel-Paho Missiong reconnect logic --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1872: CAMEL-11633 - Upgrade client mqtt paho base lib
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1872 CAMEL-11633 - Upgrade client mqtt paho base lib lib upgrade https://issues.apache.org/jira/browse/CAMEL-11633 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-11633 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1872.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1872 commit a1931a602ffe384e1b1e1ee605c31913565b045f Author: Fabrizio Spataro Date: 2017-08-04T14:31:02Z upgrade from 1.1.0 to 1.1.1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1872: CAMEL-11633 - Upgrade client mqtt paho base lib
Github user Fabryprog closed the pull request at: https://github.com/apache/camel/pull/1872 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1875: CAMEL-11642: Broken Credentials should be set from...
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/1875 CAMEL-11642: Broken Credentials should be set from endpoint https://issues.apache.org/jira/browse/CAMEL-11642 You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-11642 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/1875.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1875 commit 12923a9873cd2da5e7ef112a8cda140016cc0878 Author: Fabrizio Spataro Date: 2017-08-07T08:07:27Z Broken Credentials should be set from endpoint --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #1875: CAMEL-11642: Broker Credentials should be set from...
Github user Fabryprog closed the pull request at: https://github.com/apache/camel/pull/1875 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] camel pull request #2162: CAMEL-12118: DynamoDB: Execute query using seconda...
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/2162 CAMEL-12118: DynamoDB: Execute query using secondary indexes You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-12118 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/2162.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2162 commit 9d6ec90f45f0974956387a4a3b45522d14a447ed Author: Fabrizio Spataro Date: 2018-01-03T14:18:27Z CAMEL-12118: DynamoDB: Execute query using secondary indexes ---
[GitHub] camel pull request #2163: CAMEL-12122: S3: Add createDownloadLink functional...
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/2163 CAMEL-12122: S3: Add createDownloadLink functionality You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-12122 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/2163.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2163 commit a5cd6a7f9853e379b488af52aa7e1b20578e6031 Author: Fabrizio Spataro Date: 2018-01-04T09:09:01Z CAMEL-12122: S3: Add createDownloadLink functionality ---
[GitHub] camel pull request #2521: CAMEL-12807 Avoid to use endpoint attribute when M...
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/2521 CAMEL-12807 Avoid to use endpoint attribute when MqttConnectOptions i⦠â¦s declared once Hello, this is my propose patch to camel-paho endpoint Note is backward compatible! You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-12807 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/2521.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2521 commit a962be45274d37d7610c6dd3bdfb90365b4a0d42 Author: Fabrizio Spataro Date: 2018-09-13T13:37:45Z CAMEL-12807 Avoid to use endpoint attribute when MqttConnectOptions is declared once ---
[GitHub] camel pull request #2522: New Component IOTA
GitHub user Fabryprog opened a pull request: https://github.com/apache/camel/pull/2522 New Component IOTA You can merge this pull request into a Git repository by running: $ git pull https://github.com/Fabryprog/camel CAMEL-12815 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/camel/pull/2522.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2522 commit 77bd586c81447bf7aab58b49272dc206f6bbabbc Author: fabryprog Date: 2018-09-16T15:48:44Z New Component IOTA ---
[GitHub] camel pull request #2522: New Component IOTA
Github user Fabryprog closed the pull request at: https://github.com/apache/camel/pull/2522 ---
