db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (DERBY-4153) Document that starting with 10.5 network server will attempt to create the trace directory if it does not exist
Date Mon, 07 Dec 2009 19:17:18 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kim Haase reopened DERBY-4153:
------------------------------


I'm really sorry, I should have caught this before. I assumed that if HTML was successfully
generated, then the ant command must have run without errors -- but this is not the case.
There's an error for this file:

 [pipeline] [Error] tadminadv804410.dita:60:8: The content of element type "step" must match
"(cmd,(info|substeps|tutorialinfo|stepxmp|choicetable|choices)*,stepresult?)".

The problem is that there are <p> elements directly inside the step, when they need
to be inside the stepxmp element. 

There's also an error for cadminconfig86869.dita, which was committed for a JIRA issue that
I can't find -- I must have deleted the commit message. It was somewhere around 11/23, though.

 [pipeline] [Error] cadminconfig86869.dita:37:13: The content of element type "shortdesc"
must match "(ph|codeph|synph|filepath|msgph|userinput|systemoutput|b|u|i|tt|sup|sub|uicontrol|menucascade|term|q|boolean|state|keyword|option|parmname|apiname|cmdname|msgnum|varname|wintitle|tm|image)".
 
There's now a <ul> in the shortdesc, which isn't allowed. The simplest solution is to
do without the shortdesc and just move the whole thing, as a <p>, into the conbody.

There's another one for the Getting Started changes that I'll mention for that JIRA.

I think these errors may be the reason why the latest Derby documentation has not been generated
since 11/30. They prevent the PDF and HTML single files from being created. I'll attach a
diffs file that corrects these.

> Document that starting with 10.5 network server will attempt to create the trace directory
if it does not exist
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4153
>                 URL: https://issues.apache.org/jira/browse/DERBY-4153
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.6.0.0
>            Reporter: Kathey Marsden
>            Assignee: Bryan Pendleton
>            Priority: Minor
>             Fix For: 10.6.0.0
>
>         Attachments: docs.diff, docs.diff, docs.diff, radminconfigdb2jdrdatracedirectory.html,
radminconfigdb2jdrdatracedirectory.html, radminconfigdb2jdrdatracedirectory.html, tadminadv804410.html,
tadminadv804410.html, tadminadv804410.html
>
>
> Starting with 10.5, Network server will attempt to create the trace directory (and any
parent directories) if they do not exist.  This will require that the derbynet.jar permit
verification of the existence of the named trace directory and all necessary parent directories.
 For each directory created, the policy will require
> permission java.io.FilePermission "<directory>", "read,write"
> and the trace directory will require
> permission java.io.FilePermission "<trace directory>${/}/-", "write"

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


Mime
View raw message