On 2/1/11 2:16 AM, Claus Ibsen wrote:
Hi
I have now committed the grunt work of the slf4j migration.
Tomorrow I will migrate the remaining camel components, examples and the likes.
You should now be able to commit major stuff to camel-core or the likes.
You are welcome to run tests on your
Hi
The migration is almost complete. I added a TODO about a Logger class
in Camel which would clash with the Logger in slf4j. So I gave it a
temporary name as CamelLogger. I will rename that to a more
appropriate name.
As the migration involves a lot of changes, you are very welcome to
give the
Hi
I have just committed the last pieces of the puzzle. I think we are done now.
I may have missed something, if so let me know.
I have updated the release notes.
As usual feedback on running the examples is much welcome. Both
running using ANT and Maven.
And also when you do that from the kit
Hi
I am migrating from commons-logging to slf4j which means alot of files
will be touched by switching the logger.
https://issues.apache.org/jira/browse/CAMEL-3605?focusedCommentId=12988746#comment-12988746
There is a migrating tool to do this, so that part is easy
Claus, if you do it incrementally, and commit only one major component at a
time (the small ones could go together) it will be less painful for you and
others.
Many thanks for the heads up.
Hadrian
On Jan 31, 2011, at 7:51 AM, Claus Ibsen wrote:
Hi
I am migrating from commons-logging to
Hi
Okay seems ready for one of the first commits for the migration.
There is an issue with OSGi blueprint, which I will have to revisit.
That OSGi stuff can as usual be a bit tricky to decipher wtf is wrong.
On Mon, Jan 31, 2011 at 3:37 PM, Claus Ibsen claus.ib...@gmail.com wrote:
On Mon, Jan
Not sure what the issue is, but pax-logging 1.5.x only supports slf4j
= 1.5.11, so you need to make sure the range of the package uses is
large enough to support existing versions. I'd recommend using
1.5.11 for the slfaj-api and not 1.6.x, unless there are strong
requirements to do so.
On Mon,
On Mon, Jan 31, 2011 at 5:14 PM, Guillaume Nodet gno...@gmail.com wrote:
Not sure what the issue is, but pax-logging 1.5.x only supports slf4j
= 1.5.11, so you need to make sure the range of the package uses is
large enough to support existing versions. I'd recommend using
1.5.11 for the
Yes, it's the case. I've release pax-logging a few days ago, however,
ServiceMix is still using karaf 2.1.x which hasn't upgraded to
pax-logging 1.6.x, so I'd rather keep using 1.5.11 if possible for the
api.
Or use 1.6.x on the maven side, but make sure that the osgi range is [1.5,2.0)
On Mon,
Yeah:
Karaf 2.1.x uses PAX logging 1.5.x and SLF4J 1.5.8.
Karaf 2.2.x uses PAX logging 1.6.0 (that Guillaume and I have released
last week), PAX logging 1.6.0 supports SLF4J 1.6.1.
Regards
JB
On 01/31/2011 05:25 PM, Claus Ibsen wrote:
On Mon, Jan 31, 2011 at 5:14 PM, Guillaume
Hi
I have now committed the grunt work of the slf4j migration.
Tomorrow I will migrate the remaining camel components, examples and the likes.
You should now be able to commit major stuff to camel-core or the likes.
You are welcome to run tests on your system to see if the migrated
caused any
11 matches
Mail list logo
