Just a heads up in case anyone was not aware:
http://in.relation.to/Bloggers/JBossMavenRepositoryChanges
--
st...@hibernate.org
http://hibernate.org
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/h
On 04/15/2010 07:39 AM, Niall DOWNEY wrote:
> Hi All,
> I work for IBM and we are investigating adding our solidDB dialect to the
> existing set in Hibernate. Can someone tell me how we go about this and who
> should we talk to ?.
>
> Apologies if this is off-topic but it was suggested in the "Hibe
Hi Chris,
thanks for the info. Is it just a case of checking out the latest Test
Suite code from CVS and running what are probably JUnit tests ?. Is there
anything else we need to do or be aware of ?.
Regards,
Niall
IBM Ireland Information Services Limited registered in Ireland with number
97537
On 04/16/2010 05:48 PM, Niall DOWNEY wrote:
> Hi Chris,
> thanks for the info. Is it just a case of checking out the latest Test
> Suite code from CVS and running what are probably JUnit tests ?. Is there
> anything else we need to do or be aware of ?.
Take a look at this page: http://hibernate.or
In terms of actually getting it included? Well just passing the
testsuite is of course a first step.
Beyond that though I am a little leery of adding new dialects "just
because someone contributed (dumped) it". The reasoning is quite
simple. We have quite a bit of this type of "integration c
We discussed some other ways to deal with Dialects in the past:
http://lists.jboss.org/pipermail/hibernate-dev/2008-September/003323.html
I still like Option 3 -- make the Dialect available with the JDBC driver
distribution but I don't know of anyone doing this today.
-CB
On 04/16/2010 12:38 P
So lets say the 11am slot then for now (I know this works better for
Gail). Here is a list of things I would like to discuss:
1) 3.6
2) Documentation consolidation
3) docs site
4) git / hg
5) others?
Not sure we will get to all of them in the first go around, but we'll
work on it.
On 04/15/201
On Apr 16, 2010, at 11:38 AM, Steve Ebersole wrote:
> In terms of actually getting it included? Well just passing the
> testsuite is of course a first step.
>
> Beyond that though I am a little leery of adding new dialects "just
> because someone contributed (dumped) it". The reasoning is q
why hibernate core and hibernate common annotations use different version
identifiers?
e.g. for core
http://repository.jboss.com/maven2/org/hibernate/hibernate-core/3.5.0-Final/
for common annotations
http://repository.jboss.com/maven2/org/hibernate/hibernate-commons-annotations/3.2.0.Final/
is t
as that jdbc4 issue has been resolved, so i don't know if there is any specific
reason that we cant apply this :
Index: parent/pom.xml
===
--- parent/pom.xml (revision 19221)
+++ parent/pom.xml (working copy)
@@ -132,7 +132
10 matches
Mail list logo
