From bab3379536c528d577a9b7ebde3fd8bb91c481b0 Mon Sep 17 00:00:00 2001 From: James Hamilton Date: Thu, 2 Mar 2023 14:23:44 +0100 Subject: [PATCH] Remove manual mentions of WTK plugin (#322) The WTK plugin no longer exists. --- .../manual/troubleshooting/troubleshooting.md | 4 +-- docs/md/manual/wtk.md | 29 ------------------- 2 files changed, 1 insertion(+), 32 deletions(-) delete mode 100644 docs/md/manual/wtk.md diff --git a/docs/md/manual/troubleshooting/troubleshooting.md b/docs/md/manual/troubleshooting/troubleshooting.md index e5e48f4b..6e859d16 100644 --- a/docs/md/manual/troubleshooting/troubleshooting.md +++ b/docs/md/manual/troubleshooting/troubleshooting.md @@ -531,9 +531,7 @@ there might be several reasons: it's because these emulators don't like packageless classes and/or overloaded fields and methods. You can work around it by not using the options `-repackageclasses ''` and - [`-overloadaggressively`](../configuration/usage.md#overloadaggressively). If you're using - the JME WTK plugin, you can adapt the configuration - `proguard/wtk/default.pro` that's inside the `proguard.jar`. + [`-overloadaggressively`](../configuration/usage.md#overloadaggressively). **Failing midlets** (on a Java Micro Edition device) : If your midlet runs in an emulator and on some devices, but not on some diff --git a/docs/md/manual/wtk.md b/docs/md/manual/wtk.md deleted file mode 100644 index a78fba9d..00000000 --- a/docs/md/manual/wtk.md +++ /dev/null @@ -1,29 +0,0 @@ -**ProGuard** can be seamlessly integrated in Oracle's Wireless Toolkit (WTK) -for Java Micro Edition (JME). - -The WTK already comes with a plug-in for ProGuard. Alternatively, ProGuard -offers its own plug-in. This latter implementation is recommended, as it more -up to date and it solves some problems. It is also somewhat more efficient, -invoking the ProGuard engine directly, instead of writing out a configuration -file and running ProGuard in a separate virtual machine. - -In order to integrate this plug-in in the toolkit, you'll have to put the -following lines in the file {j2mewtk.dir}`/wtklib/Linux/ktools.properties` or -{j2mewtk.dir}`\wtklib\Windows\ktools.properties` (whichever is applicable). - - obfuscator.runner.class.name: proguard.wtk.ProGuardObfuscator - obfuscator.runner.classpath: /usr/local/java/proguard/lib/proguard.jar - -Please make sure the class path is set correctly for your system. - -Once ProGuard has been set up, you can apply it to your projects as part of -the build process. The build process is started from the WTK menu bar: - -**Project → Package → Create Obfuscated Package** - -This option will compile, shrink, obfuscate, verify, and install your midlets -for testing. - -Should you ever need to customize your ProGuard configuration for the JME WTK, -you can adapt the configuration file `proguard/wtk/default.pro` that's inside -the `proguard.jar`.