Home | History | Annotate | Download | only in manual 
      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 <script type="text/javascript" language="JavaScript">
      9 <!--
     10 if (window.self==window.top)
     11   window.top.location.replace("../index.html#"+window.location.pathname+window.location.hash);
     12 else {
     13   var hash="#"+window.location.pathname.replace(window.top.location.pathname.replace("index.html", ""), "");
     14   if (window.top.location.hash!=hash)
     15     window.top.location.hash=hash;
     16 }
     17 //-->
     18 </script>
     19 </head>
     20 <body>
     21 
     22 <h2>JME Wireless Toolkit Integration</h2>
     23 
     24 <b>ProGuard</b> can be seamlessly integrated in Oracle's Wireless Toolkit (WTK)
     25 for Java Micro Edition (JME).
     26 <p>
     27 
     28 The WTK already comes with a plug-in for ProGuard. Alternatively, ProGuard
     29 offers its own plug-in. This latter implementation is recommended, as it more
     30 up to date and it solves some problems. It is also somewhat more efficient,
     31 invoking the ProGuard engine directly, instead of writing out a configuration
     32 file and running ProGuard in a separate virtual machine.
     33 <p>
     34 
     35 In order to integrate this plug-in in the toolkit, you'll have to put the
     36 following lines in the file
     37 {j2mewtk.dir}<code>/wtklib/Linux/ktools.properties</code> or
     38 {j2mewtk.dir}<code>\wtklib\Windows\ktools.properties</code> (whichever is
     39 applicable).
     40 <p>
     41 
     42 <pre>
     43 obfuscator.runner.class.name: proguard.wtk.ProGuardObfuscator
     44 obfuscator.runner.classpath: /usr/local/java/proguard/lib/proguard.jar
     45 </pre>
     46 <p>
     47 
     48 Please make sure the class path is set correctly for your system.
     49 <p>
     50 
     51 Once ProGuard has been set up, you can apply it to your projects as part of
     52 the build process. The build process is started from the WTK menu bar:
     53 <p>
     54 <center><b>Project -> Package -> Create Obfuscated Package</b></center>
     55 <p>
     56 This option will compile, shrink, obfuscate, verify, and install your midlets
     57 for testing.
     58 <p>
     59 Should you ever need to customize your ProGuard configuration for the JME WTK,
     60 you can adapt the configuration file <code>proguard/wtk/default.pro</code>
     61 that's inside the <code>proguard.jar</code>.
     62 
     63 <hr />
     64 <noscript><div><a target="_top" href="../index.html" class="button">Show menu</a></div></noscript>
     65 <address>
     66 Copyright &copy; 2002-2011
     67 <a target="other" href="http://www.lafortune.eu/">Eric Lafortune</a>.
     68 </address>
     69 </body>
     70 </html>
     71