as subject, I think we may need a 4.1.next
-
Best Regards,
Strong Liu
http://about.me/stliu/bio
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
https://github.com/hibernate/hibernate-orm/pull/273
On 13/02/2012, at 8:16 PM, Strong Liu wrote:
is there a jira? or pull request would better
-
Best Regards,
Strong Liu http://hibernate.org/>>
http://about.me/stliu/bio
On Feb 13, 2012, at 12:23 PM, Adam Bryzak wrote:
D
new hudson job
internal :
https://hudson.qa.jboss.com/hudson/job/hibernate-core-master-metamodel/
external: seems ci.jboss.org currently down, please wait for while and go there
and search "hibernate-core-master-metamodel"
looking the failures soon
-
Best Regards,
Str
In general, yes, this is what I meant.
I think on_close or after_transaction might be better connection
release mode here.
Also, I would personally be more inclined to close the "temp session"
manually there in that block. But that part is really just a
preference I think.
On Mon 13 Feb 201
Thanks Steve for such a descriptive replay. I have played a little with
SessionBuilder and probably solved the issue. Because of
great importance of
AuditProcess#doBeforeTransactionCompletion(SessionImplementor) method, please
verify my commit:
https://github.com/lukasz-antoniak/hibernate-core
Hi,
On Mon, Feb 13, 2012 at 4:38 PM, Hardy Ferentschik wrote:
> I am fine with a 3.4.2. I don't think we should put too much effort into it
> ourself, but rely on the
> community if they want more features back ported.
>
> +1 for upgrading to Lucene 3.4.0
I don't think you can upgrade to Lucene
Thank you for your quick response.
Yes, I can follow what you were suggesting in the previous email. It should be
done shortly.
As you mentioned, I had some issue to use your logger and simply used Log4J
instead as a result. I'll take a closer look at my issue and
ask you about it with some det
I am fine with a 3.4.2. I don't think we should put too much effort into it
ourself, but rely on the
community if they want more features back ported.
+1 for upgrading to Lucene 3.4.0
--Hardy
On Feb 13, 2012, at 2:45 PM, Sanne Grinovero wrote:
> I think we should release one: we already bac
I think we should release one: we already backported some important
fixes, especially because Guillaume helped with it (among others),
which was very welcome.
So I can volunteer in making the release happen as I think such
contributions should not be discouraged by lack of tag/release
credentials,
Sanne, Hardy and I don't have specific plans to release a 3.4.x. Our general
strategy is to support the latest stable branch and do new work on the next
version. Older branches are out of this equation.
But we are not against the community doing the work. A release is a bit of an
extreme as it
On 13 févr. 2012, at 10:22, Nicolas Helleringer wrote:
> Hi Emmanuel, hi all,
>
> I am not fond of Coordinates interface too :s
>
> I think we shall stick to Option 1 as it concentrates configuration
> information in one place and we can stick to default values for field names
> for ease of u
There is no specific time. It should be today though. We can announce it
tomorrow for better timing as long as the release is in Maven today.
On 13 févr. 2012, at 11:59, Sanne Grinovero wrote:
> Does it need to be released very soon?
> I'm still writing some patches and will need to update docs;
Does it need to be released very soon?
I'm still writing some patches and will need to update docs; if you
could set a deadline hour, I'll stop with patches and make sure docs
are ready.
On 10 February 2012 16:05, Sanne Grinovero wrote:
> I'm adding
> https://hibernate.onjira.com/browse/HSEARCH-9
is there a jira? or pull request would better
-
Best Regards,
Strong Liu
http://about.me/stliu/bio
On Feb 13, 2012, at 12:23 PM, Adam Bryzak wrote:
> Derby 10.7 and later support a boolean data type, DerbyTenSevenDialect
> registers the type but doesn't override the toB
Hi Emmanuel, hi all,
I am not fond of Coordinates interface too :s
I think we shall stick to Option 1 as it concentrates configuration
information in one place and we can stick to default values for field names
for ease of use. People that do have a latitude property on their beans
often named it
15 matches
Mail list logo
