Hello all, Two releases ago, EclipseME added support for MPowerPlayer, a pure Java device emulator. However the original version included J2SE and all system classes inside the definition for J2ME so that broke the auto prompter in many ways.
Although the latest release of EclipseME has not fixed these problems yet, it does allow for a workaround some people may be interested in hearing about: the short version is that J2MELIB should include only stub jars, not runtime jars. In "Properties -> J2ME -> Device Manager", one can find MPowerPlayer as an option that can be edited. Go to "Libraries". You need to delete everything except MIDP/CLDC (and the 2d/3d graphics libs if you want to keep them). You also need to edit the jar file location for MIDP/CLDC/2D/3D to those under the "stubs" folder bundled with MPowerPlayer, not the runtime jars. As far as I am aware... that should now fix the MPowerPlayer device, you may duplicate the device to provide alternatives using variations of MIDP1/MIDP2 and CLDC1/CLDC1.1. Hope this helps some people. Using this setup, I've also been able to use (CVS) MicroEmu.org to run MIDlets... but I set that up as an SWT application and added J2SE to the runtime libraries, and made sure the stub classes were at the end of the library list. It would be good if EclipseME had MicroEMU support as a device, it seems like it would be quite easy to edit the launcher info for MPowerPlayer to allow this. Cheers, Shug ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Eclipseme-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/eclipseme-users
