Binary Assemblies need updating for fetching docbook artifacts from their new 
spots under ../d/.. and putting them in the right hierarchies
-------------------------------------------------------------------------------------------------------------------------------------------

                 Key: UIMA-1920
                 URL: https://issues.apache.org/jira/browse/UIMA-1920
             Project: UIMA
          Issue Type: Bug
          Components: Build, Packaging and Test
            Reporter: Marshall Schor
            Assignee: Marshall Schor
            Priority: Minor
             Fix For: build-parent-pom-1


The binary assemblies need to fetch the documentation built with the docbook 
toolchain from the spot where that toolchain is configured to put the output - 
now under .../target/site/d/:
{noformat}
  ../target/site/d
       css
           stylesheet-html.css
       images
           [bookname]/[bookpartname]/...    <-- image files
      [bookname].html
      [bookname].pdf
 {noformat}

In the assemblies, change the source (where these files come from) to reflect 
this layout in the target/site/d directory.
Change the layout in the assemblies to preserve the relative position of the
html, images, and css files and directories, because the html has relative refs 
to these.

Both the html and PDF files support links between the various "books".  These 
links
are setup to be "relative", and assume a relative layout that looks like this:

{noformat}
  some-top-level-dir
      d
          [bookname].html
          [bookname].pdf
{noformat}

Currently, the PDF layout is presuming an extra directory above the "d",
which is inconsistent with how the html is specified.  Fix this to correspond
to how the html is arranged, by updating the build/uima-docbook-olink project,
which is where these default layouts are specified.

Change the assemblies to copy the information under site/d to the assembly
docs directory, (including the "d").



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to