Re: [hibernate-dev] New CI machine preview

2013-03-27 Thread Sanne Grinovero
First delete all files in /etc/apache2/sites-enabled/ then create: /etc/apache2/sites-enabled/default with contents: ServerName ci.hibernate.org ProxyRequests Off http://localhost:8081/*> Order deny,allow Allow from all ProxyPreserveHost on ProxyPass / http://localhost:80

Re: [hibernate-dev] New CI machine preview

2013-03-27 Thread Davide D'Alto
Good work, what configuration have you applied to apache? I'm asking so that I can apply that to the puppet scripts Davide On Wed, Mar 27, 2013 at 1:51 PM, Sanne Grinovero wrote: > You're all welcome to play with http://54.225.162.168/ > however please keep these in mind: > > - it's not the fi

Re: [hibernate-dev] Should static logger classes be avoided

2013-03-27 Thread Hardy Ferentschik
On 27 Jan 2013, at 3:28 PM, Sanne Grinovero wrote: >>> AFAIK JBoss Modules do the right thing and BVal would be loaded in its >>> own module, making it reusable without drawbacks. >> >> is that so? So multiple deployed apps can use HV and configure each >> Validator related >> log levels? How

[hibernate-dev] unexpected warn message

2013-03-27 Thread Strong Liu
seeing this when running test on master "22:34:30,288 WARN SessionFactoryImpl:1554 - HHH08: JTASessionContext being used with JDBCTransactionFactory; auto-flush will not operate correctly with getCurrentSession() " in the method of org.hibernate.internal.SessionFactoryImpl#buildCurrentSess

Re: [hibernate-dev] Should static logger classes be avoided

2013-03-27 Thread Sanne Grinovero
On 27 March 2013 14:27, Hardy Ferentschik wrote: > > On 27 Jan 2013, at 3:10 PM, Sanne Grinovero wrote: > >> I would not avoid static loggers, there are better solutions like >> making sure the "shared library" is loaded in the right classloader >> (of the container). > > ok > >> AFAIK JBoss Modu

Re: [hibernate-dev] Should static logger classes be avoided

2013-03-27 Thread Hardy Ferentschik
On 27 Jan 2013, at 3:10 PM, Sanne Grinovero wrote: > I would not avoid static loggers, there are better solutions like > making sure the "shared library" is loaded in the right classloader > (of the container). ok > AFAIK JBoss Modules do the right thing and BVal would be loaded in its > own m

Re: [hibernate-dev] Should static logger classes be avoided

2013-03-27 Thread Sanne Grinovero
I would not avoid static loggers, there are better solutions like making sure the "shared library" is loaded in the right classloader (of the container). AFAIK JBoss Modules do the right thing and BVal would be loaded in its own module, making it reusable without drawbacks. Creating logger instanc

[hibernate-dev] Should static logger classes be avoided

2013-03-27 Thread Hardy Ferentschik
Hi all, I would like to get some feedback regarding https://hibernate.atlassian.net/browse/HV-780 - "Use of static loggers prevent deployment as a shared library". Given that all Hibernate I think all Hibernate projects use static loggers I was wondering what everyone thinks. According to the

[hibernate-dev] New CI machine preview

2013-03-27 Thread Sanne Grinovero
You're all welcome to play with http://54.225.162.168/ however please keep these in mind: - it's not the final machine: don't put too much effort in creating nice build scripts as we'll reset it to clean state soon. We *might* be able to store jobs defined so far, but we might choose not to. -