[
http://jira.jboss.com/jira/browse/JBAS-5133?page=comments#action_12409700 ]
Dimitris Andreadis commented on JBAS-5133:
------------------------------------------
AS uses our maven repository to download thirdparty dependencies, but it still uses ant
for the actual build. So the jars just need to be in the maven repo, we don't care
much how each project is built.
I see we have 2 locations for hibernate:
1)
https://svn.jboss.org/repos/repository.jboss.org/maven2//org/hibernate/hi...
2)
https://svn.jboss.org/repos/repository.jboss.org/maven2//hibernate/hibern...
I'm not sure which is better. AS currently uses (2) but (1) seems more correct.
For all maven build issues better ask Paul Geir on the JBoss Build forum.
CR is fine for now.
Upgrade Hibernate to 3.3.0.CRx (from 3.2.4.SP1_CP01)
-----------------------------------------------------
Key: JBAS-5133
URL:
http://jira.jboss.com/jira/browse/JBAS-5133
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Hibernate service
Reporter: Dimitris Andreadis
Assigned To: Steve Ebersole
Priority: Critical
Fix For: JBossAS-5.0.0.CR1
An issue to track the hibernate upgrade needed by JBoss Cache.
Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0
(JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For
EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that
use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be
a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and
include it in the hibernate-int module. I'm currently working with Steve on a *much*
improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have
AS 5 use that."
The update was postponed for AS5 Beta4 (see JBAS-4725), however for CR1 (mid-March
timeframe) we'd need to have a GA version of hibernate 3.3.0.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira