On Wed, Feb 1, 2017 at 6:46 PM, Sanne Grinovero wrote:
> Great, thanks for that!
>
> One minor issue:
> currently the homepage mentions literally "Bulk-id strategies when you
> can’t use temporary tables"
> Looks like something wrong with escaping
>
Fixed.
--
Guillaume
Yeah I saw that this evening when the new post of Vlad arrived.
There shouldn't be any escaping but apparently at some point, entities are
escaped. There is an :html_entities = false option used by the atomizer
plugin that I also used but apparently it's not used at all in the
awestruct code base.
Good points Gunnar. So then we'll plan to rename hibernate-core to
hibernate-orm and the others from hibernate-{module} to
hibernate-orm-{module}.
On Tue, Jan 31, 2017 at 2:09 AM Gunnar Morling wrote:
> Agreed, it'd be the right time if we wanted to change this.
>
> I vote for 1 in case we do
Great, thanks for that!
One minor issue:
currently the homepage mentions literally "Bulk-id strategies when you
can’t use temporary tables"
Looks like something wrong with escaping?
On 1 February 2017 at 16:05, Guillaume Smet wrote:
> On Wed, Feb 1, 2017 at 4:47 PM, Guillaume Smet
> wrote:
>
>>
The underlying problem is still unfixed[1]. There is a work around we
could try.
[1] https://issues.gradle.org/browse/GRADLE-2966 ->
https://github.com/gradle/gradle/issues/1061
On Wed, Feb 1, 2017 at 11:43 AM Steve Ebersole wrote:
> Most likely it is the cycle between hibernate-core and
> hi
Most likely it is the cycle between hibernate-core and
hibernate-orm-modules. Let me research a bit...
On Tue, Jan 31, 2017 at 2:34 PM andrea boriero wrote:
> rebased my old PR and it stops working, the "publishing is not yet able to
> resolve a dependency on a project with multiple different
On Wed, Feb 1, 2017 at 4:47 PM, Guillaume Smet
wrote:
>
> On Wed, Feb 1, 2017 at 4:42 PM, Gunnar Morling
> wrote:
>
>> Great news!
>>
>> One minor nitpick: letters reaching out to the bottom of the line
>> (e.g. "p", "y", "g") are cut off by one pixel or so. Can we increase
>> the box, line heig
On Wed, Feb 1, 2017 at 4:42 PM, Gunnar Morling wrote:
> Great news!
>
> One minor nitpick: letters reaching out to the bottom of the line
> (e.g. "p", "y", "g") are cut off by one pixel or so. Can we increase
> the box, line height or whatever is needed for it?
>
I think it's a preexisting issu
Great news!
One minor nitpick: letters reaching out to the bottom of the line
(e.g. "p", "y", "g") are cut off by one pixel or so. Can we increase
the box, line height or whatever is needed for it?
2017-02-01 16:38 GMT+01:00 Guillaume Smet :
> Hi,
>
> FYI, I just fixed the issue and the blogs p
Great, thanks
On Wed, Feb 1, 2017 at 3:38 PM, Guillaume Smet wrote:
> Hi,
>
> FYI, I just fixed the issue and the blogs posts are now featured on the
> website again.
>
> The good news:
> - we don't rely on an external service anymore
> - there is no cache so new blog posts are displayed on the w
Hi,
FYI, I just fixed the issue and the blogs posts are now featured on the
website again.
The good news:
- we don't rely on an external service anymore
- there is no cache so new blog posts are displayed on the website as soon
as the blog post is published
The in.relation.to blog now generates
+1 for fail fast
I think we generally aim for that as a good practice - when doable -
and I suspect people expect it.
On 1 February 2017 at 10:33, Gunnar Morling wrote:
> Hi,
>
> JPA defines for validation mode "auto" that bean validation must occur
> if a BV provider is present and that no vali
Hi,
JPA defines for validation mode "auto" that bean validation must occur
if a BV provider is present and that no validation shall occur
otherwise.
What should happen though if a BV provider such as HV is present but
it fails to bootstrap? In case of HV this happens if no expression
language imp
13 matches
Mail list logo
