...
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="82ba196dde5b6916-c91ad2ad-46c048c6-b03396a1-9ccb1b0e09bf5da504ac4374"><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="d35b5133fe5e1d8f-8e1e0c06-4e134909-a0f18855-6d9589f17a45c96ce1a34576"><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="e2408ee14870b7e4-a1640839-4b3d4e8a-ab5fa721-b9684cffddd69377b2b48193"><ac:plain-text-body><![CDATA[ | [[Ware 2008 | AA. References#Ware 08]] |
| ]]></ac:plain-text-body></ac:structured-macro> |
...