Currently, in AS7, the AS7 "org.jboss.logging" module is used by the
Hibernate (Core) module. The "org.jboss.logging" module happens to be
"3.1.0.Beta3". I think that Hibernate (4.0.x) Core needs to stay in
sync with the AS7 version of JBoss Logging.
https://github.com/jbossas/jboss-as/blob/m
What a mess a simple thing like logging had become :-(
On Fri, 04 Nov 2011 14:06:33 +0100, Sanne Grinovero
wrote:
> With some small changes we can move Hibernate Search to JBoss Logging
> 3.1.0.Beta3,
> and this will work fine even for the outdated Infinispan 5.0, but a
> deployed application
With some small changes we can move Hibernate Search to JBoss Logging
3.1.0.Beta3,
and this will work fine even for the outdated Infinispan 5.0, but a
deployed application won't work on AS 7.0:
it requires an application server having Logging 3.1, or will need to
bundle this and isolate from the AS
I asked about AS7 on the AS7 mailing list; quoting David Lloyd's
answer: "AS7 is going to use 3.1.x. "
But at an early experiment showed that mixing Infinispan 5.0.x (Using
Logging 3.0.x) with Search forcing a version of 3.1.x wasn't going to
work.
I have upgraded the dependencies in Infinispan 5.
How does this relate to the bugs in the logging tools, like the one with
the
wrong debug line numbers.
Aligning with AS might be a good idea, but only if we don't introduce
regressions
in the logging.
--Hardy
On Fri, 04 Nov 2011 12:30:54 +0100, Emmanuel Bernard
wrote:
> JBoss AS 7.1 is
JBoss AS 7.1 is targeted to use JBoss Logging 3.0.1 AFAIK.
Hibernate Core 4.0 right now is using JBoss Logging 3.1.0.Beta3
// logging
logging:'org.jboss.logging:jboss-logging:3.1.0.Beta3',
logging_generator:
'org.jboss.logging:jboss-logging-generator:1.0.0.CR3',
