And see, this is exactly the kind of thing I always try to avoid... Why
did y'all decide on that approach?
On Mon, May 18, 2015 at 10:33 AM, Emmanuel Bernard <emmanuel(a)hibernate.org>
+1 I thought it was in already :)
> On 18 mai 2015, at 17:20, Steve Ebersole <steve(a)hibernate.org> wrote:
> Sorry hit send too soon :(
> Anyway.. I assume it is because we know this information from commit
> As far as the ORM one, I propose a similar change. Any objections?
> On Mon, May 18, 2015 at 10:14 AM, Steve Ebersole <steve(a)hibernate.org>
>> As far as the file header, I have often thought of condensing our ORM
>> so that is awesome information. For my own curiosity did Richard give
>> a reason that the copyright statement is not necessary?
>> On Mon, May 18, 2015 at 9:58 AM, Sanne Grinovero <sanne(a)hibernate.org>
>>>> On 18 May 2015 at 15:23, Emmanuel Bernard
>>>> Note that custom checkstyle rule implementations does not fare well
>>> with IDE checkstyle rules enforcement.
>>>> I can't make it reliably work on search and OGM.
>>> As far as I remember the problem was related with having the
>>> customisations as part of the project which is being built.
>>> I'd hope one day we could publish a common set of rules by releasing
>>> the custom as an independent project, consumed by all. We could try
>>> that already for some projects, and see if the others catch up
>>> eventually? They don't even have to use the same XML so there is some
>>> room for customizing which rules exactly each project wants to
>>> I'm not sure if that will resolve your problem but it's worth
>>> it could also slightly speed up the builds by a couple of seconds, as
>>> you wouldn't have to rebuild the checkstyle module each time.
>>> hibernate-dev mailing list
> hibernate-dev mailing list