...
Sealing a JAR file automatically enforces the requirement of keeping privileged code together. In addition, it is important to minimize the accessibility of classes and their members (see rule VOID OBJ02OBJ51-J. Minimize the accessibility of classes and their members).
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="ec6797d3c30affd0-e6502112-4057445d-8bbdb796-2cd6b3993c67d34d60afe0a8"><ac:plain-text-body><![CDATA[ | [[API 2006 | AA. References#API 06]] |
| ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="5ffa87b0457bcc58-5cb16038-4be0468d-8d58b871-e22f789468ead1e9f602c991"><ac:plain-text-body><![CDATA[ | [[McGraw 1999 | AA. References#Ware 99]] | Rule 7, If you must sign your code, put it all in one archive file | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="4f13c46221ad0176-e064d1a9-4730461d-bab6955f-7f7e8d249a101d878fffe336"><ac:plain-text-body><![CDATA[ | [[Ware 2008 | AA. References#Ware 08]] |
| ]]></ac:plain-text-body></ac:structured-macro> |
...