1 <!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2 <html> 3 <head> 4 <meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> 5 <meta http-equiv="content-style-type" content="text/css"> 6 <link rel="stylesheet" type="text/css" href="style.css"> 7 <title>ProGuard JME Wireless Toolkit Integration</title> 8 </head> 9 <body> 10 11 <script type="text/javascript" language="JavaScript"> 12 <!-- 13 if (window.self==window.top) 14 document.write('<a class="largebutton" target="_top" href="../index.html#manual/wtk.html">ProGuard index</a> <a class="largebutton" target="_top" href="http://www.saikoa.com/dexguard">DexGuard</a> <a class="largebutton" target="_top" href="http://www.saikoa.com/">Saikoa</a> <a class="largebutton" target="other" href="http://sourceforge.net/projects/proguard/">Sourceforge</a>') 15 //--> 16 </script> 17 <noscript> 18 <a class="largebutton" target="_top" href="../index.html#manual/wtk.html">ProGuard index</a> 19 <a class="largebutton" target="_top" href="http://www.saikoa.com/dexguard">DexGuard</a> 20 <a class="largebutton" target="_top" href="http://www.saikoa.com/">Saikoa</a> 21 <a class="largebutton" target="other" href="http://sourceforge.net/projects/proguard/">Sourceforge</a> 22 </noscript> 23 24 <h2>JME Wireless Toolkit Integration</h2> 25 26 <b>ProGuard</b> can be seamlessly integrated in Oracle's Wireless Toolkit (WTK) 27 for Java Micro Edition (JME). 28 <p> 29 30 The WTK already comes with a plug-in for ProGuard. Alternatively, ProGuard 31 offers its own plug-in. This latter implementation is recommended, as it more 32 up to date and it solves some problems. It is also somewhat more efficient, 33 invoking the ProGuard engine directly, instead of writing out a configuration 34 file and running ProGuard in a separate virtual machine. 35 <p> 36 37 In order to integrate this plug-in in the toolkit, you'll have to put the 38 following lines in the file 39 {j2mewtk.dir}<code>/wtklib/Linux/ktools.properties</code> or 40 {j2mewtk.dir}<code>\wtklib\Windows\ktools.properties</code> (whichever is 41 applicable). 42 <p> 43 44 <pre> 45 obfuscator.runner.class.name: proguard.wtk.ProGuardObfuscator 46 obfuscator.runner.classpath: /usr/local/java/proguard/lib/proguard.jar 47 </pre> 48 <p> 49 50 Please make sure the class path is set correctly for your system. 51 <p> 52 53 Once ProGuard has been set up, you can apply it to your projects as part of 54 the build process. The build process is started from the WTK menu bar: 55 <p> 56 <center><b>Project -> Package -> Create Obfuscated Package</b></center> 57 <p> 58 This option will compile, shrink, obfuscate, verify, and install your midlets 59 for testing. 60 <p> 61 Should you ever need to customize your ProGuard configuration for the JME WTK, 62 you can adapt the configuration file <code>proguard/wtk/default.pro</code> 63 that's inside the <code>proguard.jar</code>. 64 65 <hr /> 66 <address> 67 Copyright © 2002-2014 68 <a target="other" href="http://www.lafortune.eu/">Eric Lafortune</a> @ <a target="top" href="http://www.saikoa.com/">Saikoa</a>. 69 </address> 70 </body> 71 </html> 72
