Re: [hibernate-dev] [jboss-as7-dev] Which JBoss Logging version to use in AS and Hibernate Core

[Strong Liu]

after pull all changes, I get a logging issue :(

if i run a test in IDE (IntelliJ), the log output are all like this:

17:20:31,767 DEBUG AbstractEntityPersister:576 - 
org.hibernate.internal.CoreMessageLogger_$logger
17:20:31,768 DEBUG AbstractEntityPersister:576 - 
org.hibernate.internal.CoreMessageLogger_$logger
17:20:31,768 DEBUG AbstractEntityPersister:576 - 
org.hibernate.internal.CoreMessageLogger_$logger
17:20:31,768 DEBUG AbstractEntityPersister:581 - 
org.hibernate.internal.CoreMessageLogger_$logger
17:20:31,768 DEBUG AbstractEntityPersister:581 - 
org.hibernate.internal.CoreMessageLogger_$logger
17:20:31,769 DEBUG AbstractEntityPersister:581 - 
org.hibernate.internal.CoreMessageLogger_$logger
17:20:31,769 DEBUG AbstractCollectionPersister:576 - 
org.hibernate.internal.CoreMessageLogger_$logger
17:20:31,769 DEBUG AbstractCollectionPersister:576 - 
org.hibernate.internal.CoreMessageLogger_$logger
17:20:31,769 DEBUG AbstractCollectionPersister:576 - 
org.hibernate.internal.CoreMessageLogger_$logger
17:20:31,770 DEBUG AbstractCollectionPersister:576 - 
org.hibernate.internal.CoreMessageLogger_$logger
17:20:31,770 DEBUG AbstractCollectionPersister:576 - 
org.hibernate.internal.CoreMessageLogger_$logger


but it is fine if I run it from command line

p.s. I have updated to the latest source and 'gradle cleanIdea idea clean 
test', so the dependencies in IDE are update-to-date and the generated source 
as well

any idea or am i missing some configuration here?

-
Best Regards,

Strong Liu 
http://about.me/stliu/bio

On Nov 10, 2011, at 5:35 AM, Sanne Grinovero wrote:

> Awesome!
> just verified on both Hibernate Search and Infinispan, no issues spotted !
> 
> thanks a lot,
> Sanne
> 
> 
> On 9 November 2011 21:29, Steve Ebersole  wrote:
>> Chill out man :)
>> 
>> Just making sure everyone know the ramifications and intentions.
>> 
>> On Wed 09 Nov 2011 02:43:43 PM CST, David M. Lloyd wrote:
>>> Yup, that's correct. And yeah #3 is optional which is why I said "may".
>>> 
>>> On 11/09/2011 02:38 PM, Steve Ebersole wrote:
 Thanks David!
 
 Just to make sure I understand. Doing the steps above will allow the
 built artifact to run in either AS 7.0 or 7.1. Correct?
 
 I thought we had said on IRC that Hibernate could really get away with
 (1) and (2) and that JBoss AS 7.0 could specify to use JBoss Logging 3.0
 via dep-mgmt in its pom(s) rather than allowing Hibernate (or others) to
 pull in Logging 3.1.
 
 On Wed 09 Nov 2011 02:32:11 PM CST, David M. Lloyd wrote:
> OK folks. I've pushed out jboss-logging 3.1.0.CR1 and
> jboss-logging-tools 1.0.0.CR4.
> 
> Here's what you need to do.
> 
> 0. Update your dep versions (obviously)
> 1. Add the following switch to your annotation processing step (or to
> javac if it's combined): -AloggingVersion=3.0
> 2. Build your artifacts against jboss-logging 3.1.0.CR1.
> 3. When you publish the POMs for artifacts built this way, you may
> specify jboss-logging 3.0.0.GA as the required version, and it will be
> compatible with such.
> 
> Basically what you're doing with the -AloggingVersion=3.0 flag is
> generating larger classes in exchange for backwards compatibility. If
> you develop other frameworks which are not expected to be supported on
> AS 7.0 (for example), you do not need this flag (logging version 3.1
> is required in this case).
> 
> If this doesn't solve your issues please let me know right away.
> 
> On 11/09/2011 08:47 AM, David M. Lloyd wrote:
>> Yeah, the problem was that to *implement* BasicLogger we had
>> switched to
>> using a base class (bundled in 3.1) to implement the multitude of
>> methods, due to problems associated with generating all the
>> implementations in every class.
>> 
>> On 11/09/2011 08:39 AM, Steve Ebersole wrote:
>>> Ok, I am totally confused then. I thought this was a discussion about
>>> BasicLogger. But we have been using that afaik way before our recent
>>> upgrade to 3.1
>>> 
>>> On Wed 09 Nov 2011 08:23:33 AM CST, David M. Lloyd wrote:
 On 11/09/2011 08:22 AM, Hardy Ferentschik wrote:
> On Wed, 09 Nov 2011 15:00:07 +0100, Steve Ebersole
> 
> wrote:
> 
>> Maybe instead of "shading in" the removed class you could just
>> add it
>> back to the JBoss Logging codebase?
> 
> Right, why can we not do that?
 
 You have it backwards. We didn't *remove* a class, we *added* one -
 which makes it not present in 3.0.x.
 
>> On 11/09/2011 04:48 AM, Emmanuel Bernard wrote:
>>> I see a few outputs
>>> 
>>> - JBoss Logging 3.1.0.Final is released in the next 24h and we
>>> use it
>>> in Core and Search
> 
> What's stopping a 3.1.0.Final release?
 
 Tryin

Re: [hibernate-dev] [jboss-as7-dev] Which JBoss Logging version to use in AS and Hibernate Core

[Gail Badner]

I am also seeing this, but not just when running in Intellij IDE. I'm also 
seeing it when running from the command line.

Gail

- Original Message -
> From: "Strong Liu" 
> To: "Sanne Grinovero" 
> Cc: "James Perkins" , hibernate-dev@lists.jboss.org, 
> "David M. Lloyd" 
> Sent: Monday, November 14, 2011 1:30:40 AM
> Subject: Re: [hibernate-dev] [jboss-as7-dev] Which JBoss Logging version to   
> use in AS and Hibernate Core
> 
> after pull all changes, I get a logging issue :(
> 
> if i run a test in IDE (IntelliJ), the log output are all like this:
> 
> 17:20:31,767 DEBUG AbstractEntityPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,768 DEBUG AbstractEntityPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,768 DEBUG AbstractEntityPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,768 DEBUG AbstractEntityPersister:581 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,768 DEBUG AbstractEntityPersister:581 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,769 DEBUG AbstractEntityPersister:581 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,770 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,770 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 
> 
> but it is fine if I run it from command line
> 
> p.s. I have updated to the latest source and 'gradle cleanIdea idea
> clean test', so the dependencies in IDE are update-to-date and the
> generated source as well
> 
> any idea or am i missing some configuration here?
> 
> -
> Best Regards,
> 
> Strong Liu 
> http://about.me/stliu/bio
> 
> On Nov 10, 2011, at 5:35 AM, Sanne Grinovero wrote:
> 
> > Awesome!
> > just verified on both Hibernate Search and Infinispan, no issues
> > spotted !
> > 
> > thanks a lot,
> > Sanne
> > 
> > 
> > On 9 November 2011 21:29, Steve Ebersole 
> > wrote:
> >> Chill out man :)
> >> 
> >> Just making sure everyone know the ramifications and intentions.
> >> 
> >> On Wed 09 Nov 2011 02:43:43 PM CST, David M. Lloyd wrote:
> >>> Yup, that's correct. And yeah #3 is optional which is why I said
> >>> "may".
> >>> 
> >>> On 11/09/2011 02:38 PM, Steve Ebersole wrote:
>  Thanks David!
>  
>  Just to make sure I understand. Doing the steps above will allow
>  the
>  built artifact to run in either AS 7.0 or 7.1. Correct?
>  
>  I thought we had said on IRC that Hibernate could really get
>  away with
>  (1) and (2) and that JBoss AS 7.0 could specify to use JBoss
>  Logging 3.0
>  via dep-mgmt in its pom(s) rather than allowing Hibernate (or
>  others) to
>  pull in Logging 3.1.
>  
>  On Wed 09 Nov 2011 02:32:11 PM CST, David M. Lloyd wrote:
> > OK folks. I've pushed out jboss-logging 3.1.0.CR1 and
> > jboss-logging-tools 1.0.0.CR4.
> > 
> > Here's what you need to do.
> > 
> > 0. Update your dep versions (obviously)
> > 1. Add the following switch to your annotation processing step
> > (or to
> > javac if it's combined): -AloggingVersion=3.0
> > 2. Build your artifacts against jboss-logging 3.1.0.CR1.
> > 3. When you publish the POMs for artifacts built this way, you
> > may
> > specify jboss-logging 3.0.0.GA as the required version, and it
> > will be
> > compatible with such.
> > 
> > Basically what you're doing with the -AloggingVersion=3.0 flag
> > is
> > generating larger classes in exchange for backwards
> > compatibility. If
> > you develop other frameworks which are not expected to be
> > supported on
> > AS 7.0 (for example), you do not need this flag (logging
> > version 3.1
> > is required in this case).
> > 
> > If this doesn't solve your issues please let me know right
> > away.
> > 
> > On 11/09/2011 08:47 AM, David M. Lloyd wrote:
> >> Yeah, the problem was that to *implement* BasicLogger we had
> >> switched to
> >> using a base class (bundled in 3.1) to implement the multitude
> >> of
> >> methods, due to problems associated with generating all the
> >> implementations in every class.
> >> 
> >> On 11/09/2011 08:39 AM, Steve Ebersole wrote:
> >>> Ok, I am totally confused then. I thought this was a
> >>> discussion about
> >>> BasicLogger. But we have been using that afaik way before our
> >>> recent
> >>> upgrade to 3.1
> >>> 
> >>> On Wed 09 Nov 2011 08:23:33 AM CST, David M. Lloyd wrote:
>  On 11/09/2011 08:22 A

Re: [hibernate-dev] [jboss-as7-dev] Which JBoss Logging version to use in AS and Hibernate Core

[Gail Badner]

I'm attaching the output from running o.h.test.ops.SaveOrUpdateTest.

Notice almost all of the DEBUG lines are like:
04:01:22,572 DEBUG BaseGeneralDataRegion:576 - 
org.hibernate.internal.CoreMessageLogger_$logger

This is the only one that looks correct:
4:01:22,566 DEBUG BaseGeneralDataRegion:82 - evict cache

Gail


- Original Message -
> From: "Gail Badner" 
> To: "Strong Liu" 
> Cc: "James Perkins" , hibernate-dev@lists.jboss.org, 
> "David M. Lloyd" 
> Sent: Monday, November 14, 2011 4:11:52 AM
> Subject: Re: [hibernate-dev] [jboss-as7-dev] Which JBoss Logging version  
> to  use in AS and Hibernate Core
> 
> I am also seeing this, but not just when running in Intellij IDE. I'm
> also seeing it when running from the command line.
> 
> Gail
> 
> - Original Message -
> > From: "Strong Liu" 
> > To: "Sanne Grinovero" 
> > Cc: "James Perkins" ,
> > hibernate-dev@lists.jboss.org, "David M. Lloyd"
> > 
> > Sent: Monday, November 14, 2011 1:30:40 AM
> > Subject: Re: [hibernate-dev] [jboss-as7-dev] Which JBoss Logging
> > version to  use in AS and Hibernate Core
> > 
> > after pull all changes, I get a logging issue :(
> > 
> > if i run a test in IDE (IntelliJ), the log output are all like
> > this:
> > 
> > 17:20:31,767 DEBUG AbstractEntityPersister:576 -
> > org.hibernate.internal.CoreMessageLogger_$logger
> > 17:20:31,768 DEBUG AbstractEntityPersister:576 -
> > org.hibernate.internal.CoreMessageLogger_$logger
> > 17:20:31,768 DEBUG AbstractEntityPersister:576 -
> > org.hibernate.internal.CoreMessageLogger_$logger
> > 17:20:31,768 DEBUG AbstractEntityPersister:581 -
> > org.hibernate.internal.CoreMessageLogger_$logger
> > 17:20:31,768 DEBUG AbstractEntityPersister:581 -
> > org.hibernate.internal.CoreMessageLogger_$logger
> > 17:20:31,769 DEBUG AbstractEntityPersister:581 -
> > org.hibernate.internal.CoreMessageLogger_$logger
> > 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
> > org.hibernate.internal.CoreMessageLogger_$logger
> > 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
> > org.hibernate.internal.CoreMessageLogger_$logger
> > 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
> > org.hibernate.internal.CoreMessageLogger_$logger
> > 17:20:31,770 DEBUG AbstractCollectionPersister:576 -
> > org.hibernate.internal.CoreMessageLogger_$logger
> > 17:20:31,770 DEBUG AbstractCollectionPersister:576 -
> > org.hibernate.internal.CoreMessageLogger_$logger
> > 
> > 
> > but it is fine if I run it from command line
> > 
> > p.s. I have updated to the latest source and 'gradle cleanIdea idea
> > clean test', so the dependencies in IDE are update-to-date and the
> > generated source as well
> > 
> > any idea or am i missing some configuration here?
> > 
> > -
> > Best Regards,
> > 
> > Strong Liu 
> > http://about.me/stliu/bio
> > 
> > On Nov 10, 2011, at 5:35 AM, Sanne Grinovero wrote:
> > 
> > > Awesome!
> > > just verified on both Hibernate Search and Infinispan, no issues
> > > spotted !
> > > 
> > > thanks a lot,
> > > Sanne
> > > 
> > > 
> > > On 9 November 2011 21:29, Steve Ebersole 
> > > wrote:
> > >> Chill out man :)
> > >> 
> > >> Just making sure everyone know the ramifications and intentions.
> > >> 
> > >> On Wed 09 Nov 2011 02:43:43 PM CST, David M. Lloyd wrote:
> > >>> Yup, that's correct. And yeah #3 is optional which is why I
> > >>> said
> > >>> "may".
> > >>> 
> > >>> On 11/09/2011 02:38 PM, Steve Ebersole wrote:
> >  Thanks David!
> >  
> >  Just to make sure I understand. Doing the steps above will
> >  allow
> >  the
> >  built artifact to run in either AS 7.0 or 7.1. Correct?
> >  
> >  I thought we had said on IRC that Hibernate could really get
> >  away with
> >  (1) and (2) and that JBoss AS 7.0 could specify to use JBoss
> >  Logging 3.0
> >  via dep-mgmt in its pom(s) rather than allowing Hibernate (or
> >  others) to
> >  pull in Logging 3.1.
> >  
> >  On Wed 09 Nov 2011 02:32:11 PM CST, David M. Lloyd wrote:
> > > OK folks. I've pushed out jboss-logging 3.1.0.CR1 and
> > > jboss-logging-tools 1.0.0.CR4.
> > > 
> > > Here's what you need to do.
> > > 
> > > 0. Update your dep versions (obviously)
> > > 1. Add the following switch to your annotation processing
> > > step
> > > (or to
> > > javac if it's combined): -AloggingVersion=3.0
> > > 2. Build your artifacts against jboss-logging 3.1.0.CR1.
> > > 3. When you publish the POMs for artifacts built this way,
> > > you
> > > may
> > > specify jboss-logging 3.0.0.GA as the required version, and
> > > it
> > > will be
> > > compatible with such.
> > > 
> > > Basically what you're doing with the -AloggingVersion=3.0
> > > flag
> > > is
> > > generating larger classes in exchange for backwards
> > > compatibility. If
> > > you develop other frameworks which are not expected to be
> > > supported on
> > > AS

Re: [hibernate-dev] [jboss-as7-dev] Which JBoss Logging version to use in AS and Hibernate Core

[David M. Lloyd]

Can you tell me:

1. What logging backend are you using? (log4j?)
2. Are the file/line numbers correct?

Thanks.  My suspicion is that it's a (well, another) problem in the 
log4j backend.

On 11/14/2011 03:30 AM, Strong Liu wrote:
> after pull all changes, I get a logging issue :(
>
> if i run a test in IDE (IntelliJ), the log output are all like this:
>
> 17:20:31,767 DEBUG AbstractEntityPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,768 DEBUG AbstractEntityPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,768 DEBUG AbstractEntityPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,768 DEBUG AbstractEntityPersister:581 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,768 DEBUG AbstractEntityPersister:581 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,769 DEBUG AbstractEntityPersister:581 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,770 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,770 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
>
>
> but it is fine if I run it from command line
>
> p.s. I have updated to the latest source and 'gradle cleanIdea idea
> clean test', so the dependencies in IDE are update-to-date and the
> generated source as well
>
> any idea or am i missing some configuration here?
>
> -
> Best Regards,
>
> Strong Liu http://hibernate.org>>
> http://about.me/stliu/bio
>
> On Nov 10, 2011, at 5:35 AM, Sanne Grinovero wrote:
>
>> Awesome!
>> just verified on both Hibernate Search and Infinispan, no issues spotted !
>>
>> thanks a lot,
>> Sanne
>>
>>
>> On 9 November 2011 21:29, Steve Ebersole > > wrote:
>>> Chill out man :)
>>>
>>> Just making sure everyone know the ramifications and intentions.
>>>
>>> On Wed 09 Nov 2011 02:43:43 PM CST, David M. Lloyd wrote:
 Yup, that's correct. And yeah #3 is optional which is why I said "may".

 On 11/09/2011 02:38 PM, Steve Ebersole wrote:
> Thanks David!
>
> Just to make sure I understand. Doing the steps above will allow the
> built artifact to run in either AS 7.0 or 7.1. Correct?
>
> I thought we had said on IRC that Hibernate could really get away with
> (1) and (2) and that JBoss AS 7.0 could specify to use JBoss
> Logging 3.0
> via dep-mgmt in its pom(s) rather than allowing Hibernate (or
> others) to
> pull in Logging 3.1.
>
> On Wed 09 Nov 2011 02:32:11 PM CST, David M. Lloyd wrote:
>> OK folks. I've pushed out jboss-logging 3.1.0.CR1 and
>> jboss-logging-tools 1.0.0.CR4.
>>
>> Here's what you need to do.
>>
>> 0. Update your dep versions (obviously)
>> 1. Add the following switch to your annotation processing step (or to
>> javac if it's combined): -AloggingVersion=3.0
>> 2. Build your artifacts against jboss-logging 3.1.0.CR1.
>> 3. When you publish the POMs for artifacts built this way, you may
>> specify jboss-logging 3.0.0.GA as the required version, and it will be
>> compatible with such.
>>
>> Basically what you're doing with the -AloggingVersion=3.0 flag is
>> generating larger classes in exchange for backwards compatibility. If
>> you develop other frameworks which are not expected to be supported on
>> AS 7.0 (for example), you do not need this flag (logging version 3.1
>> is required in this case).
>>
>> If this doesn't solve your issues please let me know right away.
>>
>> On 11/09/2011 08:47 AM, David M. Lloyd wrote:
>>> Yeah, the problem was that to *implement* BasicLogger we had
>>> switched to
>>> using a base class (bundled in 3.1) to implement the multitude of
>>> methods, due to problems associated with generating all the
>>> implementations in every class.
>>>
>>> On 11/09/2011 08:39 AM, Steve Ebersole wrote:
 Ok, I am totally confused then. I thought this was a discussion
 about
 BasicLogger. But we have been using that afaik way before our recent
 upgrade to 3.1

 On Wed 09 Nov 2011 08:23:33 AM CST, David M. Lloyd wrote:
> On 11/09/2011 08:22 AM, Hardy Ferentschik wrote:
>> On Wed, 09 Nov 2011 15:00:07 +0100, Steve Ebersole
>> mailto:st...@hibernate.org>>
>> wrote:
>>
>>> Maybe instead of "shading in" the removed class you could just
>>> add it
>>> back to the JBoss Logging codebase?
>>
>> Right, why can we not do that?

Re: [hibernate-dev] [jboss-as7-dev] Which JBoss Logging version to use in AS and Hibernate Core

[Strong Liu]

On Nov 14, 2011, at 11:16 PM, David M. Lloyd wrote:

> Can you tell me:
> 
> 1. What logging backend are you using? (log4j?)

yes, log4j, see below
slf4jVersion = "1.6.1"
// logging for testing
slf4j_api:  'org.slf4j:slf4j-api:' + slf4jVersion,
slf4j_log4j12:  'org.slf4j:slf4j-log4j12:' + slf4jVersion,
jcl_slf4j:  'org.slf4j:jcl-over-slf4j:' + slf4jVersion,
jcl_api:
'commons-logging:commons-logging-api:99.0-does-not-exist',
jcl:'commons-logging:commons-logging:99.0-does-not-exist',

> 2. Are the file/line numbers correct?
> 

file is correct, but line numbers are not


> Thanks.  My suspicion is that it's a (well, another) problem in the log4j 
> backend.
> 
> On 11/14/2011 03:30 AM, Strong Liu wrote:
>> after pull all changes, I get a logging issue :(
>> 
>> if i run a test in IDE (IntelliJ), the log output are all like this:
>> 
>> 17:20:31,767 DEBUG AbstractEntityPersister:576 -
>> org.hibernate.internal.CoreMessageLogger_$logger
>> 17:20:31,768 DEBUG AbstractEntityPersister:576 -
>> org.hibernate.internal.CoreMessageLogger_$logger
>> 17:20:31,768 DEBUG AbstractEntityPersister:576 -
>> org.hibernate.internal.CoreMessageLogger_$logger
>> 17:20:31,768 DEBUG AbstractEntityPersister:581 -
>> org.hibernate.internal.CoreMessageLogger_$logger
>> 17:20:31,768 DEBUG AbstractEntityPersister:581 -
>> org.hibernate.internal.CoreMessageLogger_$logger
>> 17:20:31,769 DEBUG AbstractEntityPersister:581 -
>> org.hibernate.internal.CoreMessageLogger_$logger
>> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
>> org.hibernate.internal.CoreMessageLogger_$logger
>> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
>> org.hibernate.internal.CoreMessageLogger_$logger
>> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
>> org.hibernate.internal.CoreMessageLogger_$logger
>> 17:20:31,770 DEBUG AbstractCollectionPersister:576 -
>> org.hibernate.internal.CoreMessageLogger_$logger
>> 17:20:31,770 DEBUG AbstractCollectionPersister:576 -
>> org.hibernate.internal.CoreMessageLogger_$logger
>> 
>> 
>> but it is fine if I run it from command line
>> 
>> p.s. I have updated to the latest source and 'gradle cleanIdea idea
>> clean test', so the dependencies in IDE are update-to-date and the
>> generated source as well
>> 
>> any idea or am i missing some configuration here?
>> 
>> -
>> Best Regards,
>> 
>> Strong Liu http://hibernate.org>>
>> http://about.me/stliu/bio
>> 
>> On Nov 10, 2011, at 5:35 AM, Sanne Grinovero wrote:
>> 
>>> Awesome!
>>> just verified on both Hibernate Search and Infinispan, no issues spotted !
>>> 
>>> thanks a lot,
>>> Sanne
>>> 
>>> 
>>> On 9 November 2011 21:29, Steve Ebersole >> > wrote:
 Chill out man :)
 
 Just making sure everyone know the ramifications and intentions.
 
 On Wed 09 Nov 2011 02:43:43 PM CST, David M. Lloyd wrote:
> Yup, that's correct. And yeah #3 is optional which is why I said "may".
> 
> On 11/09/2011 02:38 PM, Steve Ebersole wrote:
>> Thanks David!
>> 
>> Just to make sure I understand. Doing the steps above will allow the
>> built artifact to run in either AS 7.0 or 7.1. Correct?
>> 
>> I thought we had said on IRC that Hibernate could really get away with
>> (1) and (2) and that JBoss AS 7.0 could specify to use JBoss
>> Logging 3.0
>> via dep-mgmt in its pom(s) rather than allowing Hibernate (or
>> others) to
>> pull in Logging 3.1.
>> 
>> On Wed 09 Nov 2011 02:32:11 PM CST, David M. Lloyd wrote:
>>> OK folks. I've pushed out jboss-logging 3.1.0.CR1 and
>>> jboss-logging-tools 1.0.0.CR4.
>>> 
>>> Here's what you need to do.
>>> 
>>> 0. Update your dep versions (obviously)
>>> 1. Add the following switch to your annotation processing step (or to
>>> javac if it's combined): -AloggingVersion=3.0
>>> 2. Build your artifacts against jboss-logging 3.1.0.CR1.
>>> 3. When you publish the POMs for artifacts built this way, you may
>>> specify jboss-logging 3.0.0.GA as the required version, and it will be
>>> compatible with such.
>>> 
>>> Basically what you're doing with the -AloggingVersion=3.0 flag is
>>> generating larger classes in exchange for backwards compatibility. If
>>> you develop other frameworks which are not expected to be supported on
>>> AS 7.0 (for example), you do not need this flag (logging version 3.1
>>> is required in this case).
>>> 
>>> If this doesn't solve your issues please let me know right away.
>>> 
>>> On 11/09/2011 08:47 AM, David M. Lloyd wrote:
 Yeah, the problem was that to *implement* BasicLogger we had
 switched to
 using a base class (bundled in 3.1) to implement the multitude of
 methods, due to problems associated with generating all the
 implementations in every class.
 
 On 11/09/2011 08

Re: [hibernate-dev] Source links in JIRA broken

[Gunnar Morling]

I just checked some issues in HHH, HV and OGM and the FE integration
looked ok to me.

Thanks again,

--Gunnar


2011/11/14 Steve Ebersole :
> I think I have OGM working now also.  They really changed up the way this
> works.  If you see any trouble, let me know.  Thanks.
>
>
> On Fri 11 Nov 2011 10:19:39 AM CST, Steve Ebersole wrote:
>>
>> This should be working in all projects other than OGM. Still working on
>> that one. In fact it is currently best to stay away from trying to access
>> that "Source" tab on OGM issues unless you want your page to take 30+
>> seconds to render.
>>
>> On Thu 10 Nov 2011 12:06:27 PM CST, Steve Ebersole wrote:
>>>
>>> Sorry for the delay. I missed this message initially. I just asked them
>>> today about this to see where we stand. I still hope to have the "GitHub
>>> Connector" fixed at some point. But if it is not yet, then I asked them to
>>> go ahead and re-enable the other FishEye repos.
>>>
>>> On Sun 23 Oct 2011 05:33:56 AM CDT, Gunnar Morling wrote:

 Hi Steve,

> They want to "watch it for a couple of days to see how the performance
> is",
> then they will re-enable the others.

 At least for HV the integration is still disabled (see [1] for an
 example). Did you get any news from Atlassian here?

 Thanks,

 --Gunnar


 [1]
 https://hibernate.onjira.com/browse/HV-480?page=com.atlassian.jirafisheyeplugin%3Afisheye-issuepanel#issue-tabs


 2011/9/30 Gunnar Morling:
>
> Thanks for the update. Great to see FE working again.
>
> --Gunnar
>
>
> 2011/9/29 Steve Ebersole:
>>
>> So apparently there are issues with the direct GitHub connector. The
>> Atlassian dev team is working on that stuff. But in the meantime
>> Atlassian
>> have re-enabled the FishEye repository so that we can get linking. For
>> the
>> time being they have only restarted the Hibernate-Core Fisheye repo.
>> They
>> want to "watch it for a couple of days to see how the performance is",
>> then
>> they will re-enable the others.
>>
>>
>> On Mon 26 Sep 2011 08:36:16 AM CDT, Steve Ebersole wrote:
>>>
>>> Yeah I am aware. I have been working with Atlassian/Contegix to get
>>> that
>>> working again.
>>>
>>> On Sun 25 Sep 2011 12:32:41 PM CDT, Gunnar Morling wrote:

 Hi,

 I just noticed that the connection between JIRA issues and the
 associated sources in FishEye/GitHub seems to be broken.

 Taking HHH-5938 as example, the "GitHub" tab [1] is empty while the
 "Source" tab [2] displays the following error message:

 ===
 Repository Hibernate-Core on http://fisheye2.atlassian.com/ failed:
 Error in remote call to 'FishEye 0 (http://fisheye2.atlassian.com/)'
 (http://fisheye2.atlassian.com)
 [AbstractRestCommand{path='api/rest/query', params={query=select
 revisions from dir / where comment matches 'HHH-5938' order by date
 group by changeset return csid, rep=Hibernate-Core},
 methodType=POST}]
 : repository not in correct state: Repository is stopped
 ===

 Does anybody know what the cause is or whom to address in order to
 have this fixed?

 Apologies in case the issue is already known/being worked on.

 --Gunnar

 [1]

 https://hibernate.onjira.com/browse/HHH-5938?page=com.atlassian.jira.plugins.jira-github-connector-plugin%3Agithub-commits-tabpanel#issue-tabs
 [2]

 https://hibernate.onjira.com/browse/HHH-5938?page=com.atlassian.jirafisheyeplugin%3Afisheye-issuepanel#issue-tabs
 ___
 hibernate-dev mailing list
 hibernate-dev@lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>>
>>
>> --
>> st...@hibernate.org
>> http://hibernate.org
>>
>
>>>
>>
>
> --
> st...@hibernate.org
> http://hibernate.org
>

___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] [jboss-as7-dev] Which JBoss Logging version to use in AS and Hibernate Core

[David M. Lloyd]

I may have a fix.  Is there any way you can check out and install the 
latest jboss-logging-tools, and try to recompile with that and see if 
the issue still exists?

On 11/14/2011 09:23 AM, Strong Liu wrote:
>
>
> On Nov 14, 2011, at 11:16 PM, David M. Lloyd wrote:
>
>> Can you tell me:
>>
>> 1. What logging backend are you using? (log4j?)
>
> yes, log4j, see below
> slf4jVersion = "1.6.1"
> // logging for testing
> slf4j_api: 'org.slf4j:slf4j-api:' + slf4jVersion,
> slf4j_log4j12: 'org.slf4j:slf4j-log4j12:' + slf4jVersion,
> jcl_slf4j: 'org.slf4j:jcl-over-slf4j:' + slf4jVersion,
> jcl_api: 'commons-logging:commons-logging-api:99.0-does-not-exist',
> jcl: 'commons-logging:commons-logging:99.0-does-not-exist',
>
>> 2. Are the file/line numbers correct?
>>
>
> file is correct, but line numbers are not
>
>
>> Thanks. My suspicion is that it's a (well, another) problem in the
>> log4j backend.
>>
>> On 11/14/2011 03:30 AM, Strong Liu wrote:
>>> after pull all changes, I get a logging issue :(
>>>
>>> if i run a test in IDE (IntelliJ), the log output are all like this:
>>>
>>> 17:20:31,767 DEBUG AbstractEntityPersister:576 -
>>> org.hibernate.internal.CoreMessageLogger_$logger
>>> 17:20:31,768 DEBUG AbstractEntityPersister:576 -
>>> org.hibernate.internal.CoreMessageLogger_$logger
>>> 17:20:31,768 DEBUG AbstractEntityPersister:576 -
>>> org.hibernate.internal.CoreMessageLogger_$logger
>>> 17:20:31,768 DEBUG AbstractEntityPersister:581 -
>>> org.hibernate.internal.CoreMessageLogger_$logger
>>> 17:20:31,768 DEBUG AbstractEntityPersister:581 -
>>> org.hibernate.internal.CoreMessageLogger_$logger
>>> 17:20:31,769 DEBUG AbstractEntityPersister:581 -
>>> org.hibernate.internal.CoreMessageLogger_$logger
>>> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
>>> org.hibernate.internal.CoreMessageLogger_$logger
>>> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
>>> org.hibernate.internal.CoreMessageLogger_$logger
>>> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
>>> org.hibernate.internal.CoreMessageLogger_$logger
>>> 17:20:31,770 DEBUG AbstractCollectionPersister:576 -
>>> org.hibernate.internal.CoreMessageLogger_$logger
>>> 17:20:31,770 DEBUG AbstractCollectionPersister:576 -
>>> org.hibernate.internal.CoreMessageLogger_$logger
>>>
>>>
>>> but it is fine if I run it from command line
>>>
>>> p.s. I have updated to the latest source and 'gradle cleanIdea idea
>>> clean test', so the dependencies in IDE are update-to-date and the
>>> generated source as well
>>>
>>> any idea or am i missing some configuration here?
>>>
>>> -
>>> Best Regards,
>>>
>>> Strong Liu http://hibernate.org>
>>> >
>>> http://about.me/stliu/bio
>>>
>>> On Nov 10, 2011, at 5:35 AM, Sanne Grinovero wrote:
>>>
 Awesome!
 just verified on both Hibernate Search and Infinispan, no issues
 spotted !

 thanks a lot,
 Sanne


 On 9 November 2011 21:29, Steve Ebersole >>> 
 > wrote:
> Chill out man :)
>
> Just making sure everyone know the ramifications and intentions.
>
> On Wed 09 Nov 2011 02:43:43 PM CST, David M. Lloyd wrote:
>> Yup, that's correct. And yeah #3 is optional which is why I said
>> "may".
>>
>> On 11/09/2011 02:38 PM, Steve Ebersole wrote:
>>> Thanks David!
>>>
>>> Just to make sure I understand. Doing the steps above will allow the
>>> built artifact to run in either AS 7.0 or 7.1. Correct?
>>>
>>> I thought we had said on IRC that Hibernate could really get away
>>> with
>>> (1) and (2) and that JBoss AS 7.0 could specify to use JBoss
>>> Logging 3.0
>>> via dep-mgmt in its pom(s) rather than allowing Hibernate (or
>>> others) to
>>> pull in Logging 3.1.
>>>
>>> On Wed 09 Nov 2011 02:32:11 PM CST, David M. Lloyd wrote:
 OK folks. I've pushed out jboss-logging 3.1.0.CR1 and
 jboss-logging-tools 1.0.0.CR4.

 Here's what you need to do.

 0. Update your dep versions (obviously)
 1. Add the following switch to your annotation processing step
 (or to
 javac if it's combined): -AloggingVersion=3.0
 2. Build your artifacts against jboss-logging 3.1.0.CR1.
 3. When you publish the POMs for artifacts built this way, you may
 specify jboss-logging 3.0.0.GA as the required version, and it
 will be
 compatible with such.

 Basically what you're doing with the -AloggingVersion=3.0 flag is
 generating larger classes in exchange for backwards
 compatibility. If
 you develop other frameworks which are not expected to be
 supported on
 AS 7.0 (for example), you do not need this flag (logging version 3.1
 is required in this case).

 If this doesn't solve your issues please let me know right away.

 On 11

[hibernate-dev] Move team meeting 2 hours earlier?

[Gail Badner]

I discussed moving the team meeting two hours earlier on Tuesday with some of 
you. IIRC, Steve E., Strong, and Hardy are OK with this change.

That would be at 14:00 UTC (6am Seattle; 8 am Austin/St Louis; 9pm Beijing).

Would that work for everyone?

If so, should we start 11/15?

Thanks,
Gail
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] [jboss-as7-dev] Which JBoss Logging version to use in AS and Hibernate Core

[Strong Liu]

David,

the fix works :)

-
Best Regards,

Strong Liu 
http://about.me/stliu/bio

On Nov 15, 2011, at 1:53 AM, David M. Lloyd wrote:

> I may have a fix.  Is there any way you can check out and install the latest 
> jboss-logging-tools, and try to recompile with that and see if the issue 
> still exists?
> 
> On 11/14/2011 09:23 AM, Strong Liu wrote:
>> 
>> 
>> On Nov 14, 2011, at 11:16 PM, David M. Lloyd wrote:
>> 
>>> Can you tell me:
>>> 
>>> 1. What logging backend are you using? (log4j?)
>> 
>> yes, log4j, see below
>> slf4jVersion = "1.6.1"
>> // logging for testing
>> slf4j_api: 'org.slf4j:slf4j-api:' + slf4jVersion,
>> slf4j_log4j12: 'org.slf4j:slf4j-log4j12:' + slf4jVersion,
>> jcl_slf4j: 'org.slf4j:jcl-over-slf4j:' + slf4jVersion,
>> jcl_api: 'commons-logging:commons-logging-api:99.0-does-not-exist',
>> jcl: 'commons-logging:commons-logging:99.0-does-not-exist',
>> 
>>> 2. Are the file/line numbers correct?
>>> 
>> 
>> file is correct, but line numbers are not
>> 
>> 
>>> Thanks. My suspicion is that it's a (well, another) problem in the
>>> log4j backend.
>>> 
>>> On 11/14/2011 03:30 AM, Strong Liu wrote:
 after pull all changes, I get a logging issue :(
 
 if i run a test in IDE (IntelliJ), the log output are all like this:
 
 17:20:31,767 DEBUG AbstractEntityPersister:576 -
 org.hibernate.internal.CoreMessageLogger_$logger
 17:20:31,768 DEBUG AbstractEntityPersister:576 -
 org.hibernate.internal.CoreMessageLogger_$logger
 17:20:31,768 DEBUG AbstractEntityPersister:576 -
 org.hibernate.internal.CoreMessageLogger_$logger
 17:20:31,768 DEBUG AbstractEntityPersister:581 -
 org.hibernate.internal.CoreMessageLogger_$logger
 17:20:31,768 DEBUG AbstractEntityPersister:581 -
 org.hibernate.internal.CoreMessageLogger_$logger
 17:20:31,769 DEBUG AbstractEntityPersister:581 -
 org.hibernate.internal.CoreMessageLogger_$logger
 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
 org.hibernate.internal.CoreMessageLogger_$logger
 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
 org.hibernate.internal.CoreMessageLogger_$logger
 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
 org.hibernate.internal.CoreMessageLogger_$logger
 17:20:31,770 DEBUG AbstractCollectionPersister:576 -
 org.hibernate.internal.CoreMessageLogger_$logger
 17:20:31,770 DEBUG AbstractCollectionPersister:576 -
 org.hibernate.internal.CoreMessageLogger_$logger
 
 
 but it is fine if I run it from command line
 
 p.s. I have updated to the latest source and 'gradle cleanIdea idea
 clean test', so the dependencies in IDE are update-to-date and the
 generated source as well
 
 any idea or am i missing some configuration here?
 
 -
 Best Regards,
 
 Strong Liu http://hibernate.org>
 >
 http://about.me/stliu/bio
 
 On Nov 10, 2011, at 5:35 AM, Sanne Grinovero wrote:
 
> Awesome!
> just verified on both Hibernate Search and Infinispan, no issues
> spotted !
> 
> thanks a lot,
> Sanne
> 
> 
> On 9 November 2011 21:29, Steve Ebersole  
> > wrote:
>> Chill out man :)
>> 
>> Just making sure everyone know the ramifications and intentions.
>> 
>> On Wed 09 Nov 2011 02:43:43 PM CST, David M. Lloyd wrote:
>>> Yup, that's correct. And yeah #3 is optional which is why I said
>>> "may".
>>> 
>>> On 11/09/2011 02:38 PM, Steve Ebersole wrote:
 Thanks David!
 
 Just to make sure I understand. Doing the steps above will allow the
 built artifact to run in either AS 7.0 or 7.1. Correct?
 
 I thought we had said on IRC that Hibernate could really get away
 with
 (1) and (2) and that JBoss AS 7.0 could specify to use JBoss
 Logging 3.0
 via dep-mgmt in its pom(s) rather than allowing Hibernate (or
 others) to
 pull in Logging 3.1.
 
 On Wed 09 Nov 2011 02:32:11 PM CST, David M. Lloyd wrote:
> OK folks. I've pushed out jboss-logging 3.1.0.CR1 and
> jboss-logging-tools 1.0.0.CR4.
> 
> Here's what you need to do.
> 
> 0. Update your dep versions (obviously)
> 1. Add the following switch to your annotation processing step
> (or to
> javac if it's combined): -AloggingVersion=3.0
> 2. Build your artifacts against jboss-logging 3.1.0.CR1.
> 3. When you publish the POMs for artifacts built this way, you may
> specify jboss-logging 3.0.0.GA as the required version, and it
> will be
> compatible with such.
> 
> Basically what you're doing with the -AloggingVersion=3.0 flag is
> generating larger classes in exchange for backwards
> co

Re: [hibernate-dev] [jboss-as7-dev] Which JBoss Logging version to use in AS and Hibernate Core

[David M. Lloyd]

Pushed out 1.0.0.CR5.  Thanks for verifying!

On 11/14/2011 08:53 PM, Strong Liu wrote:
> David,
>
> the fix works :)
>
> -
> Best Regards,
>
> Strong Liu http://hibernate.org>>
> http://about.me/stliu/bio
>
> On Nov 15, 2011, at 1:53 AM, David M. Lloyd wrote:
>
>> I may have a fix. Is there any way you can check out and install the
>> latest jboss-logging-tools, and try to recompile with that and see if
>> the issue still exists?
>>
>> On 11/14/2011 09:23 AM, Strong Liu wrote:
>>>
>>>
>>> On Nov 14, 2011, at 11:16 PM, David M. Lloyd wrote:
>>>
 Can you tell me:

 1. What logging backend are you using? (log4j?)
>>>
>>> yes, log4j, see below
>>> slf4jVersion = "1.6.1"
>>> // logging for testing
>>> slf4j_api: 'org.slf4j:slf4j-api:' + slf4jVersion,
>>> slf4j_log4j12: 'org.slf4j:slf4j-log4j12:' + slf4jVersion,
>>> jcl_slf4j: 'org.slf4j:jcl-over-slf4j:' + slf4jVersion,
>>> jcl_api: 'commons-logging:commons-logging-api:99.0-does-not-exist',
>>> jcl: 'commons-logging:commons-logging:99.0-does-not-exist',
>>>
 2. Are the file/line numbers correct?

>>>
>>> file is correct, but line numbers are not
>>>
>>>
 Thanks. My suspicion is that it's a (well, another) problem in the
 log4j backend.

 On 11/14/2011 03:30 AM, Strong Liu wrote:
> after pull all changes, I get a logging issue :(
>
> if i run a test in IDE (IntelliJ), the log output are all like this:
>
> 17:20:31,767 DEBUG AbstractEntityPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,768 DEBUG AbstractEntityPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,768 DEBUG AbstractEntityPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,768 DEBUG AbstractEntityPersister:581 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,768 DEBUG AbstractEntityPersister:581 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,769 DEBUG AbstractEntityPersister:581 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,769 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,770 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
> 17:20:31,770 DEBUG AbstractCollectionPersister:576 -
> org.hibernate.internal.CoreMessageLogger_$logger
>
>
> but it is fine if I run it from command line
>
> p.s. I have updated to the latest source and 'gradle cleanIdea idea
> clean test', so the dependencies in IDE are update-to-date and the
> generated source as well
>
> any idea or am i missing some configuration here?
>
> -
> Best Regards,
>
> Strong Liu http://hibernate.org>
> 
> >
> http://about.me/stliu/bio
>
> On Nov 10, 2011, at 5:35 AM, Sanne Grinovero wrote:
>
>> Awesome!
>> just verified on both Hibernate Search and Infinispan, no issues
>> spotted !
>>
>> thanks a lot,
>> Sanne
>>
>>
>> On 9 November 2011 21:29, Steve Ebersole > 
>> 
>> > wrote:
>>> Chill out man :)
>>>
>>> Just making sure everyone know the ramifications and intentions.
>>>
>>> On Wed 09 Nov 2011 02:43:43 PM CST, David M. Lloyd wrote:
 Yup, that's correct. And yeah #3 is optional which is why I said
 "may".

 On 11/09/2011 02:38 PM, Steve Ebersole wrote:
> Thanks David!
>
> Just to make sure I understand. Doing the steps above will
> allow the
> built artifact to run in either AS 7.0 or 7.1. Correct?
>
> I thought we had said on IRC that Hibernate could really get away
> with
> (1) and (2) and that JBoss AS 7.0 could specify to use JBoss
> Logging 3.0
> via dep-mgmt in its pom(s) rather than allowing Hibernate (or
> others) to
> pull in Logging 3.1.
>
> On Wed 09 Nov 2011 02:32:11 PM CST, David M. Lloyd wrote:
>> OK folks. I've pushed out jboss-logging 3.1.0.CR1 and
>> jboss-logging-tools 1.0.0.CR4.
>>
>> Here's what you need to do.
>>
>> 0. Update your dep versions (obviously)
>> 1. Add the following switch to your annotation processing step
>> (or to
>> javac if it's combined): -AloggingVersion=3.0
>> 2. Build your artifacts against jboss-logging 3.1.0.CR1.
>> 3. When you publish the POMs for artifacts built this way, yo