Version 1.6.6 Released
Craig Setera — February 24, 2007 @ 3:30 pm — New Releases
Version 1.6.6 of EclipseME has been released. This version provides a small set of bug fixes against version 1.6.5, in addition to the ability to directly launch an emulator against an arbitrary JavaME Application Descriptor URL. Refer to Version 1.6.0 Released for more information on the new features that were recently added. It is absolutely necessary that the new installation instructions be followed in order to enable the preprocessing support as currently provided.
EclipseME requires version 3.2 of the Eclipse platform. Eclipse 3.2.2 is suggested, but 3.1 is no longer supported.
Refer to the installation instructions at http://eclipseme.org/docs/installation.html. EclipseME may be installed and updated via the EclipseME Update site as well as via an Eclipse site archive file downloadable from Sourceforge. Point Eclipse at http://eclipseme.org/updates/ to install via the update site. If you encounter issues with EclipseME, please visit http://eclipseme.org/docs/support.html for more information on support options.
This new version includes the following changes:
Enhancements
- Add ability to launch emulator against specified JAD URL (RFE 1666508)
- Increased output when System property eclipseme.log.obfuscation is set to true
- Make DeviceSelector available outside the plugin
Bug Fixes
- Fix for environment variables on 64 bit machines (Bug 1664263)
- Fix preprocessing when the project is also the source folder (Bug 1664776)
- Throw an exception if the Antenna build export template is not found (Bug 1667689)
February 27th, 2007 at 8:50 am
thx
February 27th, 2007 at 1:34 pm
I can not import the Device Definitions:-( I have Sun Java Wireless Toolkit 2.5 for CLDC, but when I set search directory c:/Program Files/ Wireless Toolkit and push the Refresh button, EclipseME find nothing. Help please!!!
February 27th, 2007 at 1:35 pm
Please bring this discussion to the user’s mailing list for support.
March 1st, 2007 at 10:15 pm
very well!
March 5th, 2007 at 9:31 am
Thanks a lot!!
March 8th, 2007 at 10:00 am
A probar!!!!
March 10th, 2007 at 10:01 am
ok
March 14th, 2007 at 7:45 pm
[…] In the Version 1.6.6 release, the ability to launch via an arbitrary JAD file was added as a new feature. Making this work required a change to the device templates used to launch emulators. This change implies the need to remove and re-import device definitions in order for the new functionality to function correctly. This detail was unfortunately not covered in the documentation. If you are encountering ClassNotFound errors, you will need to remove and re-import your device definitions in order for this new feature to function. […]
March 16th, 2007 at 5:47 am
hopefully somebody reads this …
found no better way to contact you (i don’t need another account just to post these few lines): could you please include, either in the faq or the installation-instructions, a hint that the javadoc-locations for the jar-archives could be configured in
window->preferences->j2me->device management->[a device]->edit->libraries
?
i had a hard time finding that (in fact, i created a user-library out of pure desperation) and i’m sure there are others looking for that, too.
March 16th, 2007 at 5:51 am
well, and those locations should be bound to the _jar_-archive _not_ the device! all devices of at least the wtk of sun use these jars — why should i configure these locations for each device again?
March 19th, 2007 at 6:49 pm
I am unable to get any of the devices from the sprint 3.1 toolkit to show up in the devices list. I updated to this version of eclipsme, removed all previous devices from the device list, and when i try to reimport it cannot find any devices even though i have tried every directory up to almost the roor of c:\ … any words of advice?
March 22nd, 2007 at 7:16 pm
matt,
Feel free to write up an enhancement request. I don’t have any specifics about why this toolkit may or may not be working.
Craig
April 20th, 2007 at 9:24 am
i need this software