...
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 OBJ51-J. Minimize the accessibility of classes and their members).
Noncompliant Code Example (Privileged Code)
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="991825cfa36ee0ee-224c6061-4a474d9d-baf78cce-4a13a647a68a0390d8ea39c3"><ac:plain-text-body><![CDATA[ | [[EMA 2011 | AA. References#EMA 2011]] | Optional Package Sealing | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="69cf13f6ff6ae090-c7d02b31-40e74b12-a191805e-f87d6535b69d6d8a8be0be4c"><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="e3b68cef67b6d421-75fc39ff-4cb34089-b4609c78-bc7cb18c26004799d939a633"><ac:plain-text-body><![CDATA[ | [[Ware 2008 | AA. References#Ware 08]] |
| ]]></ac:plain-text-body></ac:structured-macro> |
...