10:47 a.m.
Can we upgrade to Hibernate 3.3 and if yes on which branch? Denis
don't seem to have issues with seam 2.1.2 + hibernate 3.3.1 + slf4j +
log4j + jcl-over-slf4j.jar.
PS: this would unleash Hibernate Search 3.1 (which needs Core 3.3)
10:50 a.m.
On May 29, 2009, at 10:47 , Emmanuel Bernard wrote:
Can we upgrade to Hibernate 3.3 and if yes on which branch? Denis
don't seem to have issues with seam 2.1.2 + hibernate 3.3.1 + slf4j
+ log4j + jcl-over-slf4j.jar.
PS: this would unleash Hibernate Search 3.1 (which needs Core 3.3)
We also need slf4j for RESTEasy, by the way. So +1 on moving Seam from
commons-logging to slf4j in 2.2.
1:24 p.m.
On 29 May 2009, at 09:50, Christian Bauer wrote:
On May 29, 2009, at 10:47 , Emmanuel Bernard wrote:
> Can we upgrade to Hibernate 3.3 and if yes on which branch? Denis
> don't seem to have issues with seam 2.1.2 + hibernate 3.3.1 + slf4j
> + log4j + jcl-over-slf4j.jar.
>
> PS: this would unleash Hibernate Search 3.1 (which needs Core 3.3)
We also need slf4j for RESTEasy, by the way. So +1 on moving Seam
from commons-logging to slf4j in 2.2.
Guys, Seam DOES NOT DEPEND ON commons-logging :-)
You need to nag other people (RichFaces I think - Jay, can we add this
to the RF 4 roadmap?)
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
1:53 p.m.
On May 29, 2009, at 13:24, Pete Muir wrote:
On 29 May 2009, at 09:50, Christian Bauer wrote:
>
> On May 29, 2009, at 10:47 , Emmanuel Bernard wrote:
>
>> Can we upgrade to Hibernate 3.3 and if yes on which branch? Denis
>> don't seem to have issues with seam 2.1.2 + hibernate 3.3.1 +
>> slf4j + log4j + jcl-over-slf4j.jar.
>>
>> PS: this would unleash Hibernate Search 3.1 (which needs Core 3.3)
>
>
> We also need slf4j for RESTEasy, by the way. So +1 on moving Seam
> from commons-logging to slf4j in 2.2.
Guys, Seam DOES NOT DEPEND ON commons-logging :-)
Stop yelling and answer the original question ;) I couldn't care less
about loggers.
2:01 p.m.
On 29 May 2009, at 12:53, Emmanuel Bernard wrote:
On May 29, 2009, at 13:24, Pete Muir wrote:
>
> On 29 May 2009, at 09:50, Christian Bauer wrote:
>
>>
>> On May 29, 2009, at 10:47 , Emmanuel Bernard wrote:
>>
>>> Can we upgrade to Hibernate 3.3 and if yes on which branch? Denis
>>> don't seem to have issues with seam 2.1.2 + hibernate 3.3.1 +
>>> slf4j + log4j + jcl-over-slf4j.jar.
>>>
>>> PS: this would unleash Hibernate Search 3.1 (which needs Core 3.3)
>>
>>
>> We also need slf4j for RESTEasy, by the way. So +1 on moving Seam
>> from commons-logging to slf4j in 2.2.
>
> Guys, Seam DOES NOT DEPEND ON commons-logging :-)
Stop yelling and answer the original question ;) I couldn't care
less about loggers.
Been there, done that :-p
Sanne is going to provide a patch for Seam 2.2, and Norman will apply
- the issue is https://jira.jboss.org/jira/browse/JBSEAM-4201. If
Sanne includes an HSearch upgrade in his patch (or you want to
commit), thats cool.
7:37 p.m.
On Fri, May 29, 2009 at 7:53 AM, Emmanuel Bernard <emmanuel(a)hibernate.org>wrote:
On May 29, 2009, at 13:24, Pete Muir wrote:
> On 29 May 2009, at 09:50, Christian Bauer wrote:
>
>
>> On May 29, 2009, at 10:47 , Emmanuel Bernard wrote:
>>
>> Can we upgrade to Hibernate 3.3 and if yes on which branch? Denis don't
>>> seem to have issues with seam 2.1.2 + hibernate 3.3.1 + slf4j + log4j +
>>> jcl-over-slf4j.jar.
>>>
>>> PS: this would unleash Hibernate Search 3.1 (which needs Core 3.3)
>>>
>>
>>
>> We also need slf4j for RESTEasy, by the way. So +1 on moving Seam from
>> commons-logging to slf4j in 2.2.
>>
>
> Guys, Seam DOES NOT DEPEND ON commons-logging :-)
>
Stop yelling and answer the original question ;) I couldn't care less about
loggers.
Apparently no one cares ;-) but richfaces 3.3.X currently depends on
commons-logging 1.1. There is already a discuss point for 4.0 for
dependencies, and we can adjust for RF 3.3.2 if needed.
Just let me know.
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
--
blog: http://in.relation.to/Bloggers/Jay
7:44 p.m.
On Fri, May 29, 2009 at 1:37 PM, Jay Balunas <tech4j(a)gmail.com> wrote:
On Fri, May 29, 2009 at 7:53 AM, Emmanuel Bernard <emmanuel(a)hibernate.org>wrote:
>
> On May 29, 2009, at 13:24, Pete Muir wrote:
>
>
>> On 29 May 2009, at 09:50, Christian Bauer wrote:
>>
>>
>>> On May 29, 2009, at 10:47 , Emmanuel Bernard wrote:
>>>
>>> Can we upgrade to Hibernate 3.3 and if yes on which branch? Denis don't
>>>> seem to have issues with seam 2.1.2 + hibernate 3.3.1 + slf4j + log4j +
>>>> jcl-over-slf4j.jar.
>>>>
>>>> PS: this would unleash Hibernate Search 3.1 (which needs Core 3.3)
>>>>
>>>
>>>
>>> We also need slf4j for RESTEasy, by the way. So +1 on moving Seam from
>>> commons-logging to slf4j in 2.2.
>>>
>>
>> Guys, Seam DOES NOT DEPEND ON commons-logging :-)
>>
>
> Stop yelling and answer the original question ;) I couldn't care less
> about loggers.
Apparently no one cares ;-) but richfaces 3.3.X currently depends on
commons-logging 1.1. There is already a discuss point for 4.0 for
dependencies, and we can adjust for RF 3.3.2 if needed.
I think what no one cares about is unnecessary complexity. If we can once
and for all get this over with and put it behind us so that we are all using
the same, simple logging solution, then we can develop more interesting
things ;) Thanks in advance, Jay, for bringing RichFaces inline.
-Dan
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://in.relation.to/Bloggers/Dan
NOTE: While I make a strong effort to keep up with my email on a daily
basis, personal or other work matters can sometimes keep me away
from my email. If you contact me, but don't hear back for more than a week,
it is very likely that I am excessively backlogged or the message was
caught in the spam filters. Please don't hesitate to resend a message if
you feel that it did not reach my attention.
5451
days inactive
5451
days old
6 comments
5 participants
participants (5)
-
Christian Bauer -
Dan Allen -
Emmanuel Bernard -
Jay Balunas -
Pete Muir