Version 1.7.3 Released
Craig Setera — July 15, 2007 @ 8:04 am — New Releases
Version 1.7.3 of EclipseME has been released. This version replaces the previously removed 1.7.0 version. The new release is the first to provide the new incremental deployed JAR builder functionality. With this release, all incremental building results in a valid JAR file that should be mostly deployable. In addition, support for MicroEmulator, ME4SE and Motorola has been added.
In order to use the preprocessing support, it is absolutely necessary that the new installation instructions be followed in order to enable the preprocessing support.
EclipseME requires version 3.2 of the Eclipse platform. Eclipse 3.2.2 is suggested. Eclipse 3.3 should work, but is not heavily tested at this time.
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
- Don’t sign the JAD during incremental builds (RFE 1748246)
- Always build to and run from deployed JAD/JAR combination (RFE 1711348 & Bug 1576563)
- Add support for microemu (RFE 1632324)
- Add support for me4se (RFE 1632329)
- Allow the JAR file name to be specified via the JAD file (RFE 1556424 & 1668338)
- Add MIDP 2.1 as a known profile
Bug Fixes
- Fix for /res folder not being included when packaging (Bug 1745673)
- Fix for version always incrementing during builds despite preference settings (Bug 1748893)
- Fix for explicit builds not copying over the Midlet definitions (Bug 1742956)
- Fix for build.xml file missing (again) for Antenna export (Bug 1667689)
- Fix Motorola SDK 6.4 functionality (Bug 1717077)
NOTE: Many of the Motorola emulators do not appear to function correctly under Windows Vista - Fix for explicit builds not copying over the Midlet definitions (Bug 1742956)
July 15th, 2007 at 9:00 am
[…] Version 1.7.3 of EclipseME has been released. Visit http://eclipseme.org/blog/2007/07/15/version-173-released/ for complete information. Please make sure to pay particular attention to the installation instructions at … […]
July 15th, 2007 at 9:41 pm
hello
July 16th, 2007 at 9:28 am
MicroEmu support, yay! With the death of MPowerPlayer this now enables J2ME development on OS X.
However, the MicroEmu support seems to be flawed… the referenced libraries are pulling in all my J2SE classes and the Devices -> Libraries -> Remove button does not appear to be working for me. (I’d like to use my J2ME stub libraries so that auto-complete works correctly).
July 17th, 2007 at 1:03 pm
nice
July 18th, 2007 at 5:36 am
Superb work. But, Why don’t you support “Sun Java Toolkit 1.0 for CDC” - I wanted to use eclipseme for my project (CDC based) But finally opted to use NetBeans. If there is a way to use eclipseme for CDC, please do let me know !!!
July 24th, 2007 at 12:49 am
pls
July 25th, 2007 at 10:24 am
Hi, i’m a JavaME developer and i’ve been using EclipseME for that. But there are mainly two big features EclipseME does not support debug, i mean, when a stack trace is printed it is really useless because the stack trace does not link to the source code as it does in JavaSE (you know, in JavaSE it shows the line number of the error). This feature is a really big deal for developing (by the way Netbeans does support this feature and even running in debug mode). The other feature is the posibility of working in a library based project. If you add a project to the build path those classes are not exported to the jar file but yes, it works for compiling not exporting. In order to also export the other project class files you can select export in the java build path in the tab order and export, but if you do so, the selected project becomes bad compiled or some error ocurs because the project is marked with an x or error. I think the EclipseME project is good, but you cant not miss these two features because the project may come somehow useless, i expect you to fix these problem to the next version.
Thanks.
July 27th, 2007 at 6:25 am
Manuel,
I think you misunderstand the EclipseME development. This is a *free* open-source project that is not supported. You are welcome to submit patches for inclusion of the functions you would like, but otherwise you cannot *expect* anything other than that I will do my best from release to release to do something useful and helpful.
July 29th, 2007 at 6:35 am
j2me 点滴 - 1 （资料）…
一些资料和工具的链接。个人少量的笔记。…
July 29th, 2007 at 3:35 pm
Hi,
runs now fine with 1.7.3.
I had some problems with the jar file. Now the jar file contains only required files. Propably I messed up something before.
Very good work.
Michael
July 29th, 2007 at 3:36 pm
Hi,
EclipseME 1.7.3 runs fine with Eclipse 3.3.
I had some problems with the jar file. Now the jar file contains only required files. Propably I messed up something before.
Very good work.
Michael
August 5th, 2007 at 8:21 pm
Why when I create the JAR & JAD files I get mixed up the MIDlets of the suite? For example, the MIDlet-1: “some name”, ,”some class” turns as MIDlet-3. This stated to happen when I installed the latest version, 1.7.3 I think. In older versions, MIDlets always where included in the JAD in the exact order I introduced with the JAD Editor.
August 13th, 2007 at 4:27 pm
…