[ 
https://issues.apache.org/jira/browse/DERBY-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002319#comment-14002319
 ] 

Kim Haase commented on DERBY-6217:
----------------------------------

Well, that seems to have worked. 

Committed patches DERBY-6217-2.diff, DERBY-6217-3.diff, and the modified 
docs.properties file to documentation trunk at revision 1596037. 

The next task will be to migrate to this manual the changes made to 3 topics in 
the Developer's Guide encryption section for DERBY-6537. I'll file a patch for 
that in due course.

Also, someone will have to add this manual to the list of the Latest Alpha 
Manuals on http://db.apache.org/derby/manuals/index.html so that the guide will 
be visible to others.

After that is done, the security topics can be removed from the Admin Guide and 
Developer's Guide and this issue can be resolved.

> Put all of the security documentation in a single, separate user guide
> ----------------------------------------------------------------------
>
>                 Key: DERBY-6217
>                 URL: https://issues.apache.org/jira/browse/DERBY-6217
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.11.0.0
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>         Attachments: DERBY-6217-2.diff, DERBY-6217-3.diff, DERBY-6217.diff, 
> DERBY-6217.stat, DERBY-6217.zip
>
>
> Right now the security documentation is divided among our user guides. This 
> makes is hard for customers to understand Derby's defenses and how to 
> configure all relevant security mechanisms for an application. As 
> demonstrated by the discussion on DERBY-6160, some security mechanisms 
> involve multiple Derby jar files and multiple application tiers. Material for 
> these mechanisms is scattered across the existing user guides. It would be 
> less confusing if all of Derby's security documentation were separated out 
> into a new Security Guide.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to