I see that StandardDatabaseInfoDialectResolver selects PostgresPlusDialect
for database named "EnterpriseDB". Is that still correct for Enterprise DB
Postgres Plus Advanced Server 9.4, or should PostgreSQL94Dialect be used?
Thanks,
Gail
___
hibernate-dev
http://in.relation.to/2015/12/02/hibernate-orm-505-final-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Ok, I am now for real starting the release ;)
On Wed, Dec 2, 2015 at 11:41 AM andrea boriero wrote:
> Per $subject
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
Thanks Hardy,
I'll try it tomorrow and let you know hot it worked out.
The pandoc method yields an exception for docbook -> asciidoc and the html
-> asciidoc requires too much manual intervention.
Keep in touch,
Vlad
On Wed, Dec 2, 2015 at 6:20 PM, Hardy Ferentschik
wrote:
> Hi,
>
> On Wed, D
Per $subject
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Hi,
On Wed, Dec 02, 2015 at 01:28:59PM +0200, Vlad Mihalcea wrote:
> I started migrating the 5.0 docbook documentation to asciidoctor, and,
> because there wasn't any converter for such a task, I wrote a small shell
> script which uses pandoc.
There is a converter - https://github.com/bleathem/d
I'd prefer to just not do the docbook phase; it's just unnecessary overhead
during a build.
I'd be very surprised if the asciidoctor tool chain does not allow us to
plugin CSS as well. Granted we'd have to adjust the CSS for the
styles/classes used by the asciidoctor output. I'll ask around.
On
Hi,
I started migrating the 5.0 docbook documentation to asciidoctor, and,
because there wasn't any converter for such a task, I wrote a small shell
script which uses pandoc.
I managed to generate the asciidoc files from the current docbook, by using
the html format the docbook generates. The res
