Works for me on my Mac as expected, i.e. I get the violation only when I
really add another new line.
> I'm wondering if we really want to keep this rule
Personally I like the rule, several empty lines always look a bit odd to
me. But if the check can't be executed reliably, it's surely not big l
IIRC there was an agreement that we'd not accept new dialect anymore
On May 2, 2013, at 3:41 AM, Andrew Clemons wrote:
> I'd like to follow up on the discussion started here[1]. I was asked to
> port an existing application to Hana, so my first task was to write a
> hibernate dialect for it. I'v
Can't reproduce this either. I'm wondering if we really want to keep this
rule: its benefit is limited and even before this case we had trouble with
it on windows.
On 2 May 2013 23:41, "Guillaume SCHEIBEL"
wrote:
> Hi Emmanuel,
>
> Sorry I can't reproduce it and both maven & intellij plugins are
Hi Emmanuel,
Sorry I can't reproduce it and both maven & intellij plugins are telling me
the Label class respects the rules.
Guillaume
2013/5/3 Emmanuel Bernard
> Taking OGM master, I get a checkstyle failure on one of the test file.
> But what is surprising is that I don't see new lines at t
Taking OGM master, I get a checkstyle failure on one of the test file.
But what is surprising is that I don't see new lines at the end of the
described file.
Can you guys reproduce?
Emmanuel
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @
hibernate-ogm-core ---
[debug] exec
http://in.relation.to/Bloggers/HibernateORM430Beta2Released
Hibernate ORM 4.3.0.Beta2 was just released! There's a fairly long list of
notable changes. Rather than reproduce here, please see the above blog post.
Thanks!
Brett Meyer
Red Hat Software Engineer, Hibernate
___
Eventually found a way to get around this.
If you go to Inspections on IDEA, you can disable "Checkstyle/Real-time Scan",
which is what shows the errors.
You can enable selectively in each project.
So, all good now :)
Cheers,
On May 1, 2013, at 1:15 PM, Sanne Grinovero wrote:
> I don't know
I am hoping to have a pull request ready by Monday to bring JipiJapa
(first alpha), Hibernate 4.3.0.Beta2 (or Beta1) into the expected
WildFly alpha1 build next Tuesday.
I'm currently working on JIPI-4 (need to wrap how we add AS dependencies
on Infinispan caches) which is currently hacked to d
The downside of waiting for a pull request to be merged by someone else
is that it can take away some of the fun of contributing.
Sometimes, I think sequentially and having to wait for a pull request to
be merged can hurt my flow. I'm speaking from my experience with
non-Hibernate Search proje
As usual the details are on in.relation.to - http://in.relation.to/24167.lace
--Hardy
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
I am not certain everyone follows all pull request notifications so that might
explain the lack. At least in the "NoORM" subteam (search, OGM, Validator) we
should handle pull requests for all of these projects even if its not "our"
project du jour.
On 1 mai 2013, at 19:49, Gunnar Morling wro
11 matches
Mail list logo
