Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/188
---
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 enabl
GitHub user dhirajsb opened a pull request:
https://github.com/apache/camel/pull/188
CAMEL-7487 Add support for generating API Component documentation, simplify
generated code further
You can merge this pull request into a Git repository by running:
$ git pull https://github.
The Apache Jenkins build system has built Camel.trunk.notest (build #2084)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2084/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest.jdk7 (build #30)
Status: Still Failing
Check console output at
https://builds.apache.org/job/Camel.trunk.notest.jdk7/30/ to view the results.
Having type converters available for everything helps a lot in minimising
the need to worry about return formats. You could by default return the
native Node objects and provide type converters to List>.
On 17 June 2014 20:54, Gregor Zurowski wrote:
> Hi Everyone:
>
> A recent discussion on the
Hi Everyone:
A recent discussion on the camel-users list [1] showed that the
camel-jcr component needs some enhancements to better support
real-world use cases. I would like to add query functionality, so that
users are able to submit JCR-SQL or JCR-XPath queries and retrieve
matching nodes. A pos
I just changed the configuration, now it is build with latest JDK7.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On June 17, 2014 at 9:34:03 PM, Aki Yoshida (elak
Hi Babak,
thanks for the detail.
In that case, I hope someone is doing the change for the master build soon. :-)
regards, aki
2014-06-17 15:21 GMT+02:00 Babak Vahdat :
> Hi Aki
>
> For 2.14.0 currently there's an ongoing attempt to suppor JDK 8
> https://issues.apache.org/jira/browse/CAMEL-7314
Hi Aki
For 2.14.0 currently there's an ongoing attempt to suppor JDK 8
https://issues.apache.org/jira/browse/CAMEL-7314
And looking back into the Camel releases in the past, each given release
*typically* does support 2 JDKs so that when 2.14.0 is out then we would
support both JDK 7 and 8 and ca
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/186
---
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 enabl
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/187
---
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 enabl
GitHub user kevinearls opened a pull request:
https://github.com/apache/camel/pull/187
Fix for CAMEL-7517 Expose the component options for Camel HDFS2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kevinearls/camel CAMEL-7517
A
2014-06-13 12:43 GMT+02:00 Babak Vahdat :
>
>
> Am 13.06.14 12:23 schrieb "Aki Yoshida" unter :
>
>>I noticed the full test has been red for some time at camel-barcode.
>>
>>Today, I noticed that this test is using mvn:com.google.zxing/core/3.0.0
>>and this core-3.0.0.jar was built with jdk 7
>>
>
GitHub user kevinearls opened a pull request:
https://github.com/apache/camel/pull/186
Fix for CAMEL-7516 Expose the component options for Camel HDFS
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kevinearls/camel CAMEL-7516
Al
I noticed this error a few days ago and the errors are still there as of today.
It looks like the changes come from Dhiraj, so I'm cc'ing him.
The commit log shows him as the author and committer of the change and
I am wondering if this was a pull request and merged without resetting
the commiter/
Hi Aki:
I originally added the description of these options because of [1] and
[2], but I just looked into the code and found that these options were
eventually renamed:
"CAMEL-2780 Changed the operationName to defaultOperationName and
operationNamespace to defaultOperationNamespace
git-svn-id:
The Apache Jenkins build system has built Camel.trunk.notest.jdk7 (build #29)
Status: Failure
Check console output at
https://builds.apache.org/job/Camel.trunk.notest.jdk7/29/ to view the results.
Hi Gregor,
This change is adding the operationName and operationNamespace properties
to be included in the camel-cxf's configuration documentation.
If these properties are mentioned (and in that way, their use as
recommended), we need to be clear on its semantic when there is a conflict,
namely the
Hi,
I’ve done some checking regarding licenses of Camel-Extra components and
figured, that we are currently not using any direct dependencies of any non ASF
compliant licenses within the following components:
camel-couchbase
Couchbase itself remains under a proprietary and enterprise license, th
19 matches
Mail list logo
