Re: [hibernate-dev] Hibernate documentation on GitHub

Hi, > For sure we could try and further lower the bar to contribution (e.g. > by adding "edit" links which then get you to the source on GitHub, as > some other projects do). > But I'd prefer to leave the rendered output > on jboss.org, alongside with all other JBoss project's docs. +1 - this

Re: [hibernate-dev] Hibernate documentation on GitHub

> > Last but not least, afaik the plan was that hibernate.org becomes the place > > where things would get consolidated. > > I'd really like to see them on hibernate.org: have a better > integration (including look& feel), better control the metadata to > make sure people actually find the latest

[hibernate-dev] (no subject)

I'd like to more formally deprecate the legacy bytecode enhancement starting in 5.0.4 and remove it in 5.1. The new code is superior and already feature compatible back to 5.0 Final. Any objections? ___ hibernate-dev mailing list

Re: [hibernate-dev] (no subject)

no objections On 11 November 2015 at 17:55, Steve Ebersole wrote: > I'd like to more formally deprecate the legacy bytecode enhancement > starting in 5.0.4 and remove it in 5.1. > > The new code is superior and already feature compatible back to 5.0 Final. > > Any

Re: [hibernate-dev] Hibernate documentation on GitHub

On 11 November 2015 at 09:14, Hardy Ferentschik wrote: > Hi, > >> For sure we could try and further lower the bar to contribution (e.g. >> by adding "edit" links which then get you to the source on GitHub, as >> some other projects do). > >> But I'd prefer to leave the

Re: [hibernate-dev] Hibernate documentation on GitHub

I think it makes sense to host these on hibernate.org *after* we figure out the version-specific content issues I brought up in Barcelona. However, I am kind of torn. Unless I misunderstand that would mean moving the sources out of the upstream projects into the hibernate.org git repo. I worry

[hibernate-dev] Bytecode interception and attribute name versus attribute index

As I work on HHH-10267, a thought that keeps coming up in my head is that it would be great to avoid Map lookups in the enhancement and interception code. As an example of what I mean, consider the reader for a String field named `name` which roughly looks like: public String