Github user nicolaferraro closed the pull request at:
https://github.com/apache/camel/pull/1098
---
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
GitHub user nicolaferraro opened a pull request:
https://github.com/apache/camel/pull/1100
CAMEL-10207: Fixed test configuration for Bam. Added repetition in caâ¦
â¦se of failure.
```
Results :
Tests run: 224, Failures: 0, Errors: 0, Skipped: 0
```
You ca
+1
Its always good to get a release out in the hands of the community.
On Mon, Aug 1, 2016 at 5:45 PM, Daniel Kulp wrote:
> With CXF 3.1.7 out, I’d like to do a Camel build later that week that
> incorporates it along with a bunch of other fixes to get Camel 2.17.x working
> with CXF within Ka
Github user nicolaferraro closed the pull request at:
https://github.com/apache/camel/pull/1100
---
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
GitHub user nicolaferraro opened a pull request:
https://github.com/apache/camel/pull/1101
CAMEL-10197: Fixed and added license headers
Copied it from the main pom.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nicolaferraro/cam
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1101
---
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
Github user DariusX closed the pull request at:
https://github.com/apache/camel/pull/1097
---
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
Hello,
as log4j 1.2 is EOL since a year, would it make sense to move to log4j 2 ?
---
Luca Burgazzoli
In my opinion it makes sense.
Thanks!
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix Committer
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Tuesday, August 2, 2016 2:42 PM, Luca Burgazzoli
wrote:
He
On Tue, Aug 2, 2016 at 2:42 PM, Luca Burgazzoli wrote:
> Hello,
>
> as log4j 1.2 is EOL since a year, would it make sense to move to log4j 2 ?
>
We only use it for testing. No runtime dependency.
log4j v2 did not support log4j.properties file so any migration was a
real pain as the log4j xml fi
Oh and if any migration is needed, then maybe logback is an
alternative than log4j v2?
http://logback.qos.ch
On Tue, Aug 2, 2016 at 2:50 PM, Claus Ibsen wrote:
> On Tue, Aug 2, 2016 at 2:42 PM, Luca Burgazzoli wrote:
>> Hello,
>>
>> as log4j 1.2 is EOL since a year, would it make sense to move
Well, best practice is to use a logging facade like slf4j and not some
logging implementation, like logback or log4j.
P.S. I will be grateful if someone tell me if this message can be seen
Best regards, Vitalii Tymchyshyn
Вт, 2 серп. 2016 08:53 користувач Claus Ibsen пише:
> Oh and if any migr
+1, I'd rather use some form of a facade (homegrown, slf4j, etc.)
On Tue, Aug 2, 2016 at 8:55 AM Vitalii Tymchyshyn wrote:
> Well, best practice is to use a logging facade like slf4j and not some
> logging implementation, like logback or log4j.
>
> P.S. I will be grateful if someone tell me if t
On Tue, Aug 2, 2016 at 2:55 PM, Vitalii Tymchyshyn wrote:
> Well, best practice is to use a logging facade like slf4j and not some
> logging implementation, like logback or log4j.
>
Camel uses slf4j-api as the logging facade
> P.S. I will be grateful if someone tell me if this message can be see
I see no reason to change the logging implementation for tests. If it
ain't broke, don't fix it.
On Tue, Aug 2, 2016 at 9:00 AM James Carman
wrote:
> +1, I'd rather use some form of a facade (homegrown, slf4j, etc.)
>
> On Tue, Aug 2, 2016 at 8:55 AM Vitalii Tymchyshyn wrote:
>
>> Well, best p
Yep, I meant upgrading log4j for test only, run-time should
definitively use slf4j-api (or maybe a custom facade)
---
Luca Burgazzoli
On Tue, Aug 2, 2016 at 2:50 PM, Claus Ibsen wrote:
> On Tue, Aug 2, 2016 at 2:42 PM, Luca Burgazzoli wrote:
>> Hello,
>>
>> as log4j 1.2 is EOL since a year, wo
Hi.
I am looking into improving async non-blocking camel capabilities. Few days
ago I wrote a detailed e-mail, but got no answer, not sure if it got
through
In short, I can see next areas:
* async bean language
* integration with j8 CompletableFuture
* making netty4 fully non-blocking
* switc
Doing integration tests I found that some components include logging
implementations outside the test scope, so I did a fast check:
*for comp in $(ls | grep "camel-" | grep -v ".iml"); do*
* cd $comp*
* mvn dependency:tree | grep
'log4j\|logback\|slf4j-simple\|slf4j-jdk14\|slf4j-log4j12' | grep -v
Hi
Yeah some should be removed, but mind that some 3rd party libraries
are using log4j hardcoded as dependency so not all can be removed.
But I think camel-scr is a mistake to use log4j.
Its worthwhile I think to take a look which one can be removed or not.
Feel free to log a JIRA and work on th
I logged a Jira: https://issues.apache.org/jira/browse/CAMEL-10217
On Tue, Aug 2, 2016 at 4:35 PM, Claus Ibsen wrote:
> Hi
>
> Yeah some should be removed, but mind that some 3rd party libraries
> are using log4j hardcoded as dependency so not all can be removed.
>
> But I think camel-scr is a
You can use YAML instead of XML or properties files for a nice config
format. Plus, there's a few log4j 1->2 tools out there already:
https://issues.apache.org/jira/browse/LOG4J2-1436
On 2 August 2016 at 09:48, Nicola Ferraro wrote:
> I logged a Jira: https://issues.apache.org/jira/browse/CAMEL-
Most of the log4j.properties are very simple and they looks like a
copy and paste from an ancient one
I think we can get a relative simple groovy script to do the migration
at least for components and examples.
If you think it is worth give it a try I can do it.
---
Luca Burgazzoli
On Tue, Aug
If it's only for test, what's the motivation? Is anything broken? Does
anything code directly to the API?
On Tue, Aug 2, 2016 at 11:21 AM Matt Sicker wrote:
> You can use YAML instead of XML or properties files for a nice config
> format. Plus, there's a few log4j 1->2 tools out there already:
My only motivation was to keep the dependencies up to date
---
Luca Burgazzoli
On Tue, Aug 2, 2016 at 5:50 PM, James Carman wrote:
> If it's only for test, what's the motivation? Is anything broken? Does
> anything code directly to the API?
>
> On Tue, Aug 2, 2016 at 11:21 AM Matt Sicker wro
Another motivation is that when Camel wants to work on JDK9 support, you'll
find that log4j 1.x doesn't work anymore.
On 2 August 2016 at 11:21, Luca Burgazzoli wrote:
> My only motivation was to keep the dependencies up to date
>
> ---
> Luca Burgazzoli
>
>
> On Tue, Aug 2, 2016 at 5:50 PM, Jam
Now, that's a motivation I can get behind! :)
On Tue, Aug 2, 2016 at 12:38 PM Matt Sicker wrote:
> Another motivation is that when Camel wants to work on JDK9 support, you'll
> find that log4j 1.x doesn't work anymore.
>
> On 2 August 2016 at 11:21, Luca Burgazzoli wrote:
>
> > My only motivat
GitHub user DariusX opened a pull request:
https://github.com/apache/camel/pull/1102
Camel 10075 and camel 10077 documentation fixes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/DariusX/camel
CAMEL-10075-and-CAMEL-10077-Docum
Github user DariusX closed the pull request at:
https://github.com/apache/camel/pull/1102
---
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
Github user sirlatrom closed the pull request at:
https://github.com/apache/camel/pull/1055
---
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 e
GitHub user PascalSchumacher opened a pull request:
https://github.com/apache/camel/pull/1103
CAMEL-10214: doneFileName is a common option
Explain how the doneFileName option works for consumers endpoints.
extends
https://github.com/apache/camel/commit/9943e77709010a37c8804
We have a ticket to track migration issues:
https://issues.apache.org/jira/browse/LOG4J2-1473
On 2 August 2016 at 12:24, James Carman wrote:
> Now, that's a motivation I can get behind! :)
>
>
> On Tue, Aug 2, 2016 at 12:38 PM Matt Sicker wrote:
>
> > Another motivation is that when Camel wants
GitHub user Rajesh734 opened a pull request:
https://github.com/apache/camel/pull/1104
Camel 2.17.x
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/camel camel-2.17.x
Alternatively you can review and apply these changes a
Github user Rajesh734 closed the pull request at:
https://github.com/apache/camel/pull/1104
---
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 e
GitHub user Rajesh734 opened a pull request:
https://github.com/apache/camel/pull/1105
Camel 2.17.x
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/camel camel-2.17.x
Alternatively you can review and apply these changes a
Github user Rajesh734 closed the pull request at:
https://github.com/apache/camel/pull/1105
---
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 e
Good day.
Working on a camel component for Google PubSub.
One of the ways to get high throughput is a batched consumer, where a number
of messages is received in a single API call.
The obvious choice is to push them further down the line as individual
exchanges.
This, however, poses a certain i
The Apache Jenkins build system has built Camel.2.17.x.notest (build #100)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.2.17.x.notest/100/
to view the results.
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1103
---
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
38 matches
Mail list logo
