Most esteemed developers,
I was developing some patches for Hibernate Search but as I work on it on my own
I don't have much time for it; currently some problems about the move to Maven
have completely killed my productivity.
I have found some reference on your website;
The maven guide looks good
Hi Sanne,
I just updated core to the latest and ran 'mvn clean install'. Everything
worked fine. Admittedly I had to disable
the doc profile in the master pom, because the docbook generation failed,
but that's a different issue. I am using maven 2.0.9 and JDK 1.5.0_06.
Maybe someone can mak
This is unfortunate.
These glitches were expected, and we will fix them as they pop up.
Though as Hardy said, the new HSearch build system is independent of
Hibernate Core. All the needed libraries are downloaded in build/lib/
core and build/lib/test
IM me if you need more help.
AFAIK JBoss
Any reason why we target SLF4J 1.4.2 and not 1.5?
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Currently the docbook plugin relies on some system tools for dealing
with translations. You would need the GNU GetText toolset and the KDE
poxml toolset installed to do full doc builds.
Or you could disable docs in the build by using -
DdisableDistribution=true That essentially skips the d
As Emmanuel stated the synch has already been requested by JBoss for
all the org.jboss and org.hibernate bits in the JBoss repo. From my
understanding there is a pissing contest of sorts in the way :(
Anyway, I think it makes the most sense (and most of the Maven
developers express the sam
I was really only considering XML metadata when writing that generator
and thus did not even consider the scenario of defining the identifier
annotations on a superclass.
I do not like this proposal as it completely whacks one of the
intended benefits of allowing sharing of segments between
Because 1.4.2 was just released when I did that migration, as I
already answered on that monsterous JBoss dev list thread ;)
I have no issue with upgrading as long as no issues are created by that.
On May 15, 2008, at 5:30 PM, Emmanuel Bernard wrote:
Any reason why we target SLF4J 1.4.2 and
