Hello all,
I've just release Hibernate Commons Annotations 4.0.5.Final, to fix a
single but annoying issue:
https://hibernate.atlassian.net/browse/HCANN-60
-- Sanne
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mail
Hi guys,
any chance to have this included in 4.3.6:
https://hibernate.atlassian.net/browse/HHH-9217
I have supplied a pull request - it's really simple but keeps blocking me.
--
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x1
I have been running the EE 7 compatibility tests with the Java security
manager enabled to find issues like http://pastie.org/9378079
Should we try to fix these on the ORM 4.3 branch (WildFly 9.0 currently
is using 4.3.5.Final) or on master (which should show up in WildFly at
some point)?
Scot
On 07/11/2014 07:53 AM, Petar Tahchiev wrote:
> Hello,
>
> I'm really sorry to post this here but I couldn't find any jboss-logging
> mailing list.
https://lists.jboss.org/mailman/listinfo/wildfly-dev might also be a
good place to post on. The developers that work on jboss-logging, will
see yo
Hi Sanne,
yes, as you can see:
-
So I got rid of this dependency and I added the jboss-logging. So now
here's my set of jars:
hibernate-core
hibernate-entitymanager
hibernate-c3p0
hibernate-validator
log4j2
org.jboss.logging:jboss-logging:jar:3.2.0.
Hi,
I never tried Log4j2 myself, but while excluding all jboss-logging
artifacts, are you making sure you keep at least one (compatible)
version of it?
You need JBoss Logging to log anything, even if you re-route the
actual output to a different logger, as that's what Hibernate will use
as primary
Hello,
I'm really sorry to post this here but I couldn't find any jboss-logging
mailing list. So here's my question. I'm reading this issue:
https://issues.jboss.org/browse/JBLOGGING-95
and I'm trying to make my hibernate use log4j2. So far I had
org.jboss.logging
jboss-logging-log4j
Gail, there are (at least) two other Hibernate projects waiting for that
release. Sad news!
On 10 Jul 2014 19:44, "Gail Badner" wrote:
> I am rescheduling the 4.3.6 release for Wednesday next week.
>
> That will give us enough time to do necessary backports to 4.2 and also
> release 4.2.15.
>
>