I think the slf4j-simple you suggest might work better than the slf4j-nop I
had settled upon. I just picked one out of the slf4j-1.4.2.jar that didn't
have any other downstream dependencies. I am sure slf4j-nop does absolutely
nothing (old school /dev/null style logging) whereas slf4j-simple
Thank you Troy for the detailed ticket!
A fix is up for review: http://reviewboard.liftweb.net/r/90/
slf4j-simple is preferred common denominator. slf4j-nop is
self-defeating IMHO :)
Good point regarding slf4j-log4j12 for legacy fallback. I have added an
inline note in the POM.
Cheers,
Troy,
I ran into the same problem. It seems to be a hibernate issue - that
archetype uses an older version of hibernate that breaks with mysql.
Change the version in your pom for hibernate (I don't remember the
latest, maybe 3.4GA). I meant to post this a while ago, as it cost me an
hour or
If updating the pom hibernate version fixes the problem, please file an
issue and we'll update the Archetype.
Thanks,
Derek
On Mon, Nov 2, 2009 at 6:23 AM, Chris Lewis burningodzi...@gmail.comwrote:
Troy,
I ran into the same problem. It seems to be a hibernate issue - that
archetype uses
Yes I tried Chris's suggestion, and JPA does in fact work with MySQL 5.0
with auto-increment ID columns even with columns named something other than
'id' using @Column(val name=PROJECT_TYPE_ID) for example.
Thanks Chris!
I changed JPAWeb/spa/pom.xml dependency for hibernate-entitymanager to
Troy,
Thanks for the analysis. We need to fix the pom for JPADemo archetype.
Can you please file a ticket for this
(http://github.com/dpp/liftweb/issues)?
We'll update the pom and resolve the slf4j dependencies.
Cheers, Indrajit
NB: We might just make it for M7 if all goes well. Else, it'll
