Oh, the maven plugin seems to be a different project than what I was referencing.
So is this just not possible to fix? I'd really hate to have to go back to xdoc. On Mon, 29 Apr 2019 at 11:48, Ralph Goers <[email protected]> wrote: > > The issue isn’t marked as fixed. The problem I am having is that tables are > rendered without borders. This is because asciidoc doesn’t include its css > file when building the site because the “normal” asciidoc css would break the > site. Asciidoc generates tables with css class names to generate the borders > and grids. According to the Jira issue other markup has the same issue. > > Ralph > > > On Apr 29, 2019, at 8:50 AM, Matt Sicker <[email protected]> wrote: > > > > I had converted them to asciidoc a while back because it provided more > > syntactical features than markdown. Many of the files I converted > > weren't markdown but xdoc. > > > > Also, there was a new asciidoctor release just the other day. Unsure > > if it's related. > > > > On Mon, 29 Apr 2019 at 10:34, Ralph Goers <[email protected]> > > wrote: > >> > >> The master branch was converted to use AsciiDoctor. To be honest, I don’t > >> remember why. But after trying to create a new page with it I discovered > >> that AsciiDoctor simply doesn’t work properly with the Maven Site Plugin. > >> See https://github.com/asciidoctor/asciidoctor-maven-plugin/issues/166 > >> <https://github.com/asciidoctor/asciidoctor-maven-plugin/issues/166>. As > >> such I believe the site documents in Master need to be converted back to > >> Markdown. > >> > >> Ralph > > > > > > > > -- > > Matt Sicker <[email protected]> > > > > -- Matt Sicker <[email protected]>
