GitHub user abracadabrasimsalabimhocuspocus opened a pull request:
https://github.com/apache/camel/pull/1750
CAMEL-11394: REUSE_ADDRESSES options is set using the value for
TCP_NO_DELAY inteaâ¦
The undertow endpoint configuration for the REUSE_ADDRESS option is set
using the optio
The Apache Jenkins build system has built Camel.trunk.notest (build #3290)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3290/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #3289)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3289/
to view the results.
On Mon, May 29, 2017 at 7:30 AM, Luca Burgazzoli wrote:
> It may be worth adding a small number of JMH micro benchmarks - not to
> be used as performances metrics - on camel core so we can spot
> potential regressions.
>
I just added our first JMH tests, which you can find in the
tests/camel-jmh
The Apache Jenkins build system has built Camel.trunk.notest (build #3288)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3288/
to view the results.
i want to send an XML via camel Message header to XSLT param.
in XSLT , while iterate, getting an error like,
org.apache.xpath.objects.XObject cannot be cast to
org.apache.xpath.objects.XNodeSet.
Eg: http://camel.465427.n5.nabble.com/Transformation-error-CAMEL-to-XSLT-tp5802851.html
Sent from
GitHub user snurmine opened a pull request:
https://github.com/apache/camel/pull/1749
CAMEL-11393: sql-stored - Add support for typeNames and scale in grammar
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/snurmine/camel CAMEL-1
The Apache Jenkins build system has built Camel.2.19.x.notest (build #48)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.2.19.x.notest/48/
to view the results.
Github user dmvolod closed the pull request at:
https://github.com/apache/camel/pull/1747
---
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 ena
Hi
You can fork any github repo, that is allowed for anyone to do.
For example you can fork it, do some code changes in your own branch,
and then for example build the JARs locally and share / use them
within your own company (internally). That is what companies can do to
do their own patching et
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1748
---
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 enab
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
GitHub user abracadabrasimsalabimhocuspocus opened a pull request:
https://github.com/apache/camel/pull/1748
CAMEL-11392: String to ByteBuffer conversion causes overflow due to
multibyte chars
The NIOConverter uses String.length() to allocate a ByteBuffer which may
not match the ac
GitHub user dmvolod opened a pull request:
https://github.com/apache/camel/pull/1747
Fixing misprints and change trace levels for logs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dmvolod/camel grpc-misprints
Alternatively yo
GitHub user onders86 opened a pull request:
https://github.com/apache/camel/pull/1746
CAMEL-11357 - Change examples groupId and disable publishing to Mavenâ¦
⦠central
I am not %100 sure about disabling push to Maven Central. I followed the
config here [1]
[1](h
The Apache Jenkins build system has built Camel.trunk.notest (build #3287)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3287/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #3286)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3286/
to view the results.
+1
On Fri, Jun 9, 2017 at 12:19 PM, Onder SEZGIN wrote:
> +1
>
> On Fri, 9 Jun 2017 at 11:28, Zoran Regvart wrote:
>
> > On Thu, Jun 8, 2017 at 11:36 PM, Gregor Zurowski
> > wrote:
> > > Sure, I can cut a release candidate for 2.19.1 over the weekend. Does
> > that
> > > work for everyone?
> >
The Apache Jenkins build system has built Camel.2.19.x.notest (build #47)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.2.19.x.notest/47/
to view the results.
The Apache Jenkins build system has built Camel.2.19.x.notest (build #46)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.2.19.x.notest/46/
to view the results.
+1
On Fri, 9 Jun 2017 at 11:28, Zoran Regvart wrote:
> On Thu, Jun 8, 2017 at 11:36 PM, Gregor Zurowski
> wrote:
> > Sure, I can cut a release candidate for 2.19.1 over the weekend. Does
> that
> > work for everyone?
>
> +1
>
> zoran
> --
> Zoran Regvart
>
--
Sent from my iPhone
Hi
You need to talk on the Camel Extra forum / github at camel-extra.
We do not support or maintain camel-extra here at the official Apache Camel.
IMHO camel-extra is dead, we have plenty on our plate by Apache Camel
here at Apache.
On Fri, Jun 9, 2017 at 11:43 AM, fabryprog wrote:
> Can i ha
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
On Thu, Jun 8, 2017 at 11:36 PM, Gregor Zurowski
wrote:
> Sure, I can cut a release candidate for 2.19.1 over the weekend. Does that
> work for everyone?
+1
zoran
--
Zoran Regvart
+1. Thanks Gregor.
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Thursday, June 8, 2017 11:36 PM, Gregor Zurowski
wrote:
Hi,
Sure, I can
+1
On Fri, Jun 9, 2017 at 6:10 AM, Claus Ibsen wrote:
> On Thu, Jun 8, 2017 at 11:36 PM, Gregor Zurowski
> wrote:
> > Hi,
> >
> > Sure, I can cut a release candidate for 2.19.1 over the weekend. Does
> that
> > work for everyone?
> >
>
> +1
>
> > Thanks,
> > Gregor
> >
> >
> >
> > On Jun 8, 201
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1744
---
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 enab
Thank you.I have posted to Camel users forum...
--
View this message in context:
http://camel.465427.n5.nabble.com/Predicate-With-Xpath-tp5802579p5802717.html
Sent from the Camel Development mailing list archive at Nabble.com.
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1743
---
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 enab
29 matches
Mail list logo
