Version 1.5.0 Released
Craig Setera — March 18, 2006 @ 9:33 am — New Releases
A new version of EclipseME has been released. This release is based on the new device management strategy previously described. Users of previous versions of EclipseME should make sure to read and understand the migration steps to move to this release. In addition to these feature enhancements, this version is the first to officially support the 3.2 development stream of the Eclipse platform.
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.
IMPORTANT: Beginning with Version 1.1.0, EclipseME supports only Eclipse 3.1. Support for Eclipse 3.0 is no longer included. Users of Eclipse 3.0 must use Version 1.0.0.
This new version includes the following changes:
- Complete rework of the platform definition structure into devices
- Enhancement Requests 1229119, 1445398, 1380378 and 984862
- Probable fixes due to restructuring
Bugs 1208058, 1313817, 1371166, 1434616
- Export wtk.midpapi in Antenna Build Files (Bug 1413441, RFE 1310686)
- Fixes for Eclipse 3.2 (Bug 1439113)
March 19th, 2006 at 9:47 pm
good!
March 20th, 2006 at 2:02 am
i want you to sent me about eclipseMe . Thanhk you
March 20th, 2006 at 11:34 am
This assumes all your projects are MIDP 2.0. I found that after the upgrade there was a lot of work getting my MIDP 1.0 projects to work. I had to manually create the right device profiles and rebuild all my projects.
March 20th, 2006 at 8:21 pm
I noticed the Nokia 7210 and 3510i emulators don’t show up the device lists? What’s wrong, do I need to do anything special? So far this is the only reason I am not using this version.
March 20th, 2006 at 9:33 pm
Yes, I have the same problem, Nokia 7210 Can not be detected.But under the same folder, Nokia S60 can be imported correctly~~
March 21st, 2006 at 1:41 pm
teknokrat: EclipseME is just picking up whatever configurations and profiles are provided by the toolkit devices. Hopefully it was relatively easy to add add MIDP profiles with th enew release?
March 21st, 2006 at 1:42 pm
j3 and XY:
It sounds like the two NOkia emulators are not responding correctly to UEI commands. You probably should join the EclipseME users mailing list to get some help.
March 22nd, 2006 at 6:03 am
I too am having some issues trying to get MIDP 1.0 working under WTK2.2. I’ve added a device profile, changed what jars I could to 1.0 versions, but it still retains some references (in bootclasspath) to the MIDP 2.0 jars, so I’ve been mucking about in the workspace metadata files.
I’ve convinced it to preverify and compile again, but the emulator still won’t start.
Does anyone have any detailed instructions on retrofitting MIDP 1.0 profiles into WTK2.2? Thanks.
March 22nd, 2006 at 11:12 am
EclipseME 1.5.0 发布…
EclipseME开发小组宣布EclipseME 1.5.0 版本 发布.新版本是基于新的设备管理策略, 所有用户都需要详细查看官方站点的文档, 从而了解正确的转移到新版本上来的步骤….
March 22nd, 2006 at 5:09 pm
Difficulty with EclipseME 1.5.0 / WTK 2.2…
As I’m learning Java ME, I’m currently sticking with MIDP 1.0/CLDC 1.0 — it’s a bit for the challenge, and more for wider compatibility with older hardware.
EclipseME 1.5.0 was recently released, and upon upgrading, I found that it did away with t…
March 23rd, 2006 at 4:00 am
我现在使用软件的版本是1.1.0的，你有什么理由让我用1.5.0的。
I now use the software version is 1.1.0, you let me have any reason to use 1.5.0.
March 24th, 2006 at 9:50 am
I found that RunAs no longer worked in 1.5. The emulator came up, but the Java app was not launched.
To fix it, I had to do this:
1) Open …\workspace\.metadata\.plugins\eclipseme.core\devices.xml
2) Replace "-Xdescriptor with: -Xdescriptor"
(I hope this web interface is going to properly escape the chars above)
March 24th, 2006 at 9:53 am
This web interface did not escape properly. Step 2 should read more or less like this:
2) Replace
& q u o t ;-Xdescriptor
with
-Xdescriptor& q u o t ;
(& q u o t ; but without the spaces)
There should be 4 occurrences in the XML file.
March 28th, 2006 at 9:12 pm
why WTK2.0 emulators don’t show up the device lists?
March 29th, 2006 at 12:32 am
it can’t locate the exception line in source code when debug.
March 29th, 2006 at 8:47 am
The new device management is much better!
Good work.
March 31st, 2006 at 6:49 am
how to add j2me sources to jars?
March 31st, 2006 at 6:53 am
Why I can’t make WTK 2.3 device with cldc 1.0 and midp 1.0?
Why it works only if it is set to 1.1 and 2.0?
Why I device name and device name in WTK are the same? I can’t make “DefaultColorPhone 1.0″ and “DefaultColorPhone 2.0″ as it causes problems as these names are not in WTK list.
March 31st, 2006 at 7:02 am
found about sources - but works only if javadoc is added. Why javadoc is needed, when trying to add source as source includes javadoc in it!
April 1st, 2006 at 2:42 pm
This new Eclipse ME version follows the UEI (Unified Emulator Interface), available at: http://java.sun.com/j2me/docs/uei_specs.pdf.
The Excerpt below describes what is UEI:
The Unified Emulator Interface (UEI) is a standard for interaction between Integrated Development Environments (IDEs) and device emulators. IDE vendors who implement the UEI specification know that their products will work with a wide variety of device emulators. Device manufacturers who implement the UEI specification in an emulator are assured that their emulator will work with a wide variety of development tools. Developers are happy because their tools and emulators are interoperable. Customers win because the UEI simplifies the process of creating applications.
April 2nd, 2006 at 11:01 pm
qick
April 10th, 2006 at 1:08 am
i wonder if someone has encountered the same problem as i do with eclipseme. When the program throws an exception and the stack trace is printed, the output is always something like:
java.lang.RuntimeException: assertion failed: ‘false’ in Game.paint(g)
at Def.ASSERT(+12)
at Game.paint(+146)
at javax.microedition.lcdui.Canvas.callPaint(+80)
at javax.microedition.lcdui.Display.repaint(+77)
at javax.microedition.lcdui.Display.registerNewCurrent(+237)
at javax.microedition.lcdui.Display.access$400(+6)
at javax.microedition.lcdui.Display$DisplayAccessor.foregroundNotify(+46)
at javax.microedition.lcdui.Display$DisplayManagerImpl.notifyWantsForeground(+152)
at javax.microedition.lcdui.Display$DisplayManagerImpl.access$100(+6)
at javax.microedition.lcdui.Display.setCurrentImpl(+115)
at javax.microedition.lcdui.Display.setCurrent(+29)
at Game.(+23)
at Meteos.startApp(+14)
at javax.microedition.midlet.MIDletProxy.startApp(+7)
at com.sun.midp.midlet.Scheduler.schedule(+270)
at com.sun.midp.main.Main.runLocalClass(+28)
at com.sun.midp.main.Main.main(+116)
so the location is displayed to be (+???) and i cannot locate where the exception is. can anyone help me?
April 10th, 2006 at 7:10 am
Discussions like this with the stack trace should be handled on the user’s mailing list where everyone can try to help out.
April 10th, 2006 at 11:11 pm
ok,thanks. i’ll try to post it out.
April 13th, 2006 at 10:40 am
I changed in “devices.xml” file as described in 13, but still the device is launched but the application does not run. I get the following message:
Execution completed.
0 bytecodes executed
0 thread switches
776 classes in the system (including system classes)
0 dynamic objects allocated (0 bytes)
0 garbage collections (0 bytes collected)
ALERT: Attempting to resume current thread
Execution completed.
0 bytecodes executed
0 thread switches
776 classes in the system (including system classes)
0 dynamic objects allocated (0 bytes)
0 garbage collections (0 bytes collected)
April 14th, 2006 at 4:46 am
very good
April 16th, 2006 at 5:08 pm
Nadoor,
Support is handled via the eclipseme-users mailing list. You likely need to follow the steps in http://eclipseme.org/docs/configuring.html#step4
April 17th, 2006 at 8:19 am
Please Send j2me Program to ghoghnuose@yahoo.com
April 18th, 2006 at 2:32 am
While Im probably not qualified to speak since Ive never even used EclipseME yet (I do intend to, Ive been assigned to build midlets for my company) Im also a bit worried by the removal(?) of midp1 - I hope a more elegant switching system will be put in place soon(tm)
April 22nd, 2006 at 12:33 am
I have never used EclipseMe,This is my first to use EclipseMe.
But I have used Eclipse and, Now ,I am going to use J2ME, So I am going to download EclipseMe and
install it , and Enjoy myself…
April 23rd, 2006 at 10:52 pm
Chao cac ban!
May 25th, 2006 at 12:32 pm
i am using Eclipse ,i begin to learn j2me.so i hope i can get the EclipseMe
June 10th, 2006 at 3:57 am
Alwasy hear of Eclipse, Try to test .
June 10th, 2006 at 3:58 am
Try to use j2me plugin .
June 12th, 2006 at 8:20 pm
I can’t get a successful debug session going. The first time, after install I was successful. But everyother time after I have not been. The emulator Device either start then terminates or just appears to hang. Below is the sequence after debug session is started and the device automatically terminates. Is this a configuration issue?
Message after device terminates unexpectedly: “ALERT: Attempting to resume current thread”
Waiting for KVM…
Connecting to 127.0.0.1 on port 2800
Waiting for debugger on port 1484
Running with storage root DefaultGrayPhone
Connected to KVM
Connection received.
Method…………: 10184fd4 ‘com/sun/midp/security/Permissions.getPermIndex (static)’
Stack Chunk…….: e7058c
Frame Pointer…..: e706c0
Current IP……..: 102159a7 = 1021598f + offset 24
Previous Frame….: e706a0
Previous IP…….: 102159e0 (offset 24)
Frame size……..: 2 (1 arguments, 1 local variables)
Argument[0]…….: ecb258
Local[1]……….: 5
Method…………: 10184ff4 ‘com/sun/midp/security/Permissions.setPerms (static)’
Stack Chunk…….: e7058c
Frame Pointer…..: e706a0
Current IP……..: 102159e0 = 102159c8 + offset 24
Previous Frame….: e70670
Previous IP…….: 10215b49 (offset 265)
Frame size……..: 6 (4 arguments, 2 local variables)
Argument[0]…….: ecad84
Argument[1]…….: ecab68
Argument[2]…….: 1
Argument[3]…….: 1
Local[4]……….: 0
Local[5]……….: 0
Method…………: 10185034 ‘com/sun/midp/security/Permissions.readPermissionsTable (static)’
Stack Chunk…….: e7058c
Frame Pointer…..: e70670
Current IP……..: 10215b49 = 10215a40 + offset 265
Previous Frame….: e70614
Previous IP…….: 10215c1d (offset 21)
Frame size……..: 17 (1 arguments, 16 local variables)
Argument[0]…….: ee26e0
Local[1]……….: edd804
Local[2]……….: edd0b8
Local[3]……….: edc588
Local[4]……….: ecad84
Local[5]……….: ed1374
Local[6]……….: ecb860
Local[7]……….: ed0700
Local[8]……….: ed0a08
Local[9]……….: c
Local[10]……….: ecab68
Local[11]……….: ecaf4c
Local[12]……….: 16
Local[13]……….: 0
Local[14]……….: 0
Local[15]……….: 0
Local[16]……….: 0
Method…………: 10185054 ‘com/sun/midp/security/Permissions.isValidDomainName (static)’
Stack Chunk…….: e7058c
Frame Pointer…..: e70614
Current IP……..: 10215c1d = 10215c08 + offset 21
Previous Frame….: e705f0
Previous IP…….: 101f14a4 (offset 11)
Frame size……..: 3 (2 arguments, 1 local variables)
Argument[0]…….: ee26e0
Argument[1]…….: edd828
Local[2]……….: 0
Method…………: 1016d890 ‘com/sun/midp/dev/DevMIDletSuiteImpl.create (static)’
Stack Chunk…….: e7058c
Frame Pointer…..: e705f0
Current IP……..: 101f14a4 = 101f1499 + offset 11
Previous Frame….: e705c4
Previous IP…….: 101dec7d (offset 20)
Frame size……..: 5 (5 arguments, 0 local variables)
Argument[0]…….: ee26e0
Argument[1]…….: edd864
Argument[2]…….: edd924
Argument[3]…….: 10115c10
Argument[4]…….: edd828
Method…………: 1016224c ‘com/sun/midp/main/Main.runLocalClass (static)’
Stack Chunk…….: e7058c
Frame Pointer…..: e705c4
Current IP……..: 101dec7d = 101dec69 + offset 20
Previous Frame….: e705a0
Previous IP…….: 101de6fc (offset 116)
Frame size……..: 3 (1 arguments, 2 local variables)
Argument[0]…….: ee2f88
Local[1]……….: 0
Local[2]……….: 0
Method…………: 101621ac ‘com/sun/midp/main/Main.main (static)’
Stack Chunk…….: e7058c
Frame Pointer…..: e705a0
Current IP……..: 101de6fc = 101de688 + offset 116
Previous Frame….: 0
Previous IP…….: 1
Frame size……..: 3 (1 arguments, 2 local variables)
Argument[0]…….: e70878
Local[1]……….: ee2f88
Local[2]……….: edd97c
VM status:
Instruction pointer.: 102159a7 (offset within invoking method: 24)
Next instruction….: 0×84
Frame pointer…….: e706c0
Local pointer…….: e706b8
Stack size……….: 256; sp: e706d4; ranges: e70594-e70794;ee4610-ee4810;
Contents of the current stack frame:
e706b8: ecb258 (lp)
e706bc: 5
e706c0: e706a0 (fp)
e706c4: 102159e0
e706c8: e706b4
e706cc: 10184fd4
e706d0: e7058c
e706d4: 0 (end of frame) (sp)
Execution stack contains 324 items:
e70878
ee2f88
edd97c
0
1
e70590
101621ac
e7058c
0
ee2f88
0
0
e705a0
101de6fc
e705b4
1016224c
e7058c
0
ee26e0
edd864
edd924
10115c10
edd828
e705c4
101dec7d
e705d8
1016d890
e7058c
0
ee26e0
edd828
0
e705f0
101f14a4
e70604
10185054
e7058c
0
ee26e0
edd804
edd0b8
edc588
ecad84
ed1374
ecb860
ed0700
ed0a08
c
ecab68
ecaf4c
16
0
0
0
0
e70614
10215c1d
e70628
10185034
e7058c
0
ecad84
ecab68
1
1
0
0
e70670
10215b49
e70684
10184ff4
e7058c
0
ecb258
5
e706a0
102159e0
e706b4
10184fd4
e7058c
0
Execution completed.
593436 bytecodes executed
3 thread switches
738 classes in the system (including system classes)
12647 dynamic objects allocated (666932 bytes)
3 garbage collections (539440 bytes collected)
ALERT: Attempting to resume current thread
Execution completed.
593436 bytecodes executed
3 thread switches
738 classes in the system (including system classes)
12647 dynamic objects allocated (666932 bytes)
3 garbage collections (539440 bytes collected)
June 12th, 2006 at 8:34 pm
I was able to resolve the unexpected debug session termination by configuring via “preferences” the debug session timeout as recommended. Apparently the timeout changed back to the default, although I had set it to the recommended 15000, it was back at 3000. The launch timeout was not changed, it remained at the 20000.
I hope this helps anybody with the same issue “not be able to start a successful debug session”.
Message seen at unexpected termination of debug session: ALERT: Attempting to resume current thread”