My changes are committed.
Let me know if there is any issue. especially serialization. I move to
non static instance of log in most cases.
On May 16, 2008, at 18:02, Emmanuel Bernard wrote:
Cool, I've almost completed the migration based on 1.4.2
A migration with no issue is like cake witho
Good to see Bill Burke being, well Bill Burke.
On May 16, 2008, at 5:09 PM, Bill Burke wrote:
Awesome to see two hibernate developers now spending their energy on
such an important refactoring. Keep up the good work.
Emmanuel Bernard wrote:
Cool, I've almost completed the migration based
Awesome to see two hibernate developers now spending their energy on
such an important refactoring. Keep up the good work.
Emmanuel Bernard wrote:
Cool, I've almost completed the migration based on 1.4.2
A migration with no issue is like cake without ice: not worth it ;)
On May 16, 2008, at
Cool, I've almost completed the migration based on 1.4.2
A migration with no issue is like cake without ice: not worth it ;)
On May 16, 2008, at 02:35, Steve Ebersole wrote:
Because 1.4.2 was just released when I did that migration, as I
already answered on that monsterous JBoss dev list thre
Because 1.4.2 was just released when I did that migration, as I
already answered on that monsterous JBoss dev list thread ;)
I have no issue with upgrading as long as no issues are created by that.
On May 15, 2008, at 5:30 PM, Emmanuel Bernard wrote:
Any reason why we target SLF4J 1.4.2 and
