Lines Matching full:processed
90 application to be processed. The class files in these jars will be
91 processed and written to the output jars. By default, any non-class files
103 directories). The processed input of the preceding <code>-injars</code>
107 the <a href="#filefilters">filters</a> section. Each processed class file
120 application to be processed. The files in these jars will not be included
160 to make sure the processed code remains consistent.</dd>
174 <dd>Specifies the version number to be set in the processed class files. The
236 processed code remains compatible with any originally serialized classes.
250 detect it again when processing an application that uses the processed
264 of their classes, so that the processed code can still link with the
357 making assumptions can be dangerous; you can easily break the processed
371 processed code otherwise. Only applicable when optimizing (and when
397 of the processed code on some JVMs, since advanced just-in-time
487 make the processed code even smaller (and less comprehensible). Only
569 names</a>. It can make the processed code smaller and less comprehensible.
582 make the processed code even smaller and less comprehensible. Its
625 For example, you may want to have your processed libraries and
674 <dd>Specifies not to preverify the processed class files. By default, class
677 you will need to run an external preverifier on the processed code if you
684 <dd>Specifies that the processed class files are targeted at Java Micro
718 class members are indeed required for processing, the processed code will
727 class members are indeed required for processing, the processed code will
778 <li>A jar file, in which all processed class files and resource files will be
