Yes, T5.4 trunk is already using Hibernate 4.1. If you want to use 4.1
with T5.3, you have to recompile tapestry-hibernate. See comments in
https://issues.apache.org/jira/browse/TAP5-1922.
Kalle
On Fri, Apr 27, 2012 at 5:06 AM, netdawg wrote:
> Thanks! Believe this is planned for 5.4.x...so le
Thanks! Believe this is planned for 5.4.x...so let it slide.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Upgrading-to-Hibernate-Core-4-1-1-Final-tp5669640p5670087.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
Hi,
i created a ticket for this:
https://issues.apache.org/jira/browse/TAP5-1922
Felix Scheffer
2012/4/27 netdawg
> Thanks, kristian. I tried that already (couple of times). Thanks, though.
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Upgrading-to-Hibernate
Thanks, kristian. I tried that already (couple of times). Thanks, though.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Upgrading-to-Hibernate-Core-4-1-1-Final-tp5669640p5669799.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
OK. Gave up on this, next version will probably include anyway.
For now, looks like Tapestry 3.5.2 depends on Hibernate 3.6.0.Final.
I downloaded that
http://grepcode.com/snapshot/repo1.maven.org/maven2/org.hibernate/hibernate-core/3.6.0.Final
and I am off doing useful work ;-).
Thanks,
open the pom.xml of your main application in the eclipse pom editor
and switch to the dependency tab. there you can see all the direct and
transitive dependencies. and do a clean install of all your modules..
or parent project.
On Fri, Apr 27, 2012 at 11:03 AM, netdawg wrote:
> Yes, basically the
Yes, basically the exception is a compile exception saying the following
"could not be resolved":
import org.hibernate.Session;
And, finally, I also tried this:
org.apache.tapestry
tapestry-hibernate
${tapestry-release-version}
can you post your exception?
On Fri, Apr 27, 2012 at 10:45 AM, netdawg wrote:
> Neither did this work...
>
>
> org.apache.tapestry
> tapestry-hibernate
> ${tapestry-release-version}
>
>
> org.hibernate
> hiber
Neither did this work...
org.apache.tapestry
tapestry-hibernate
${tapestry-release-version}
org.hibernate
hibernate-core
org.hibernate
hibernat
Whacking tapestry-hibernate does not help either...
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Upgrading-to-Hibernate-Core-4-1-1-Final-tp5669640p5669693.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
you have to add exclusions to your tapestry-hibernate dependency
g,
kris
On Fri, Apr 27, 2012 at 10:19 AM, Chris Mylonas wrote:
> i think tapestry-hibernate pulls in hibernate jars, so you can remove it from
> your pom
> doing it how you've done is how to break it
>
>
> On 27/04/2012, at 6:15 P
i think tapestry-hibernate pulls in hibernate jars, so you can remove it from
your pom
doing it how you've done is how to break it
On 27/04/2012, at 6:15 PM, netdawg wrote:
> Issue: Current (5.3.2) versions of Tapestry-Hibernate seem to clash with
> latest 4.1.1 Final of Hibernate core. Speci
12 matches
Mail list logo