The obfuscation does work, there is an XXX_base_obf.jar in the deployed directory. But the next step seem to fail, generating the manifest and copying the result to XXX.jar.
ANOTHER Bug: the Midlet-Version is incremented automatically, not concerning what i defined in the global or in my Project-Setting! I wonder how i can force eclipse/eclipseME to show me what he is doing... Where is the output going? Could the beta-builds output more info to track down the error? Markus Ben Hutchison schrieb: > Ben Hutchison wrote: > >> I have identified 2 problems with obfuscation in 1.7.0.b in my >> environment (Eclipse 3.3.0 Windows): >> >> 1. The generated JAD file shows the JAR size unobfuscated, and does not >> match the true JAR size. >> >> 2. Apparently, every 2nd run of the obfuscator does not obfuscate. >> >> > Im experiencing a 3rd bug in 1.7.0.b packaging: The Manifest file is > always omitted from the JAR file, thus resulting in an invalid Midlet > that cannot be run. > > -Ben > -- ********************************* [EMAIL PROTECTED] http://www.psitronic.de psitronic IT-Solutions Markus Sinner W-Rathenau-Str. 14 - 68642 Bürstadt Tel.: (+49)6206 / 963513 Fax: (+49)6206 / 963514 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Eclipseme-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/eclipseme-users
