I have compiled a little list of options for Java ME and Java SE, which i would put on brainstorm. i'd like to get a few comments on it here first, though

these are mostly options allnameswereout mentioned. i have no idea about the compatibility of open source implementations with the official one. maybe someone could elaborate on that.

i also put in the possibilities of nokia porting open source implementations of SE and ME, though i'm not sure that's even realistic, since it would mean effort without being able to say "Java compatible". if you think these options are not even worth mentioning i will leave them out.



Proposal 1:
Java ME

nokia buys Java ME royalities and lets sun port it
+) official implementation, official support
-) probably quite expensive
-) Closed License

community ports phoneme
more info
+) GPL
-) no team as of yet
-) not "official", so no advertising of MIDP capability
-) no info as to how complete this implementation is

nokia ports phoneme
+-) see above

nokia or the community ports a Java SE implementation,
and we use smth. like microemu for ME compatibility
+-) see above
-) might be a bit slower



Proposal 2:
Java SE

nokia buys java SE embedded royalities and lets sun port it
+) official implementation, official support
-) probably quite expensive
-) Closed License

community ports OpenJDK/JRE 6
more info
+) GPL
-) no team as of yet
-) not "official", so no advertising
-) no info as to how complete this implementation is

nokia ports OpenJDK/JRE 6
+-) see above

community ports Jalimo
+) GPL
-) not much activity lately
-) no advertising, maybe incomplete

Do you by any chance remember that Nokia already ships J2ME VM with both S40 and S60 phones? In other words, Nokia already has a PhoneME implementation.

Why should "community" port Jalimo which is already ported to the tablet and has packages available from Diablo Extras?

Where does Iced Tea fit in with all these options?

yes, but not for Maemo. and even if porting from S60 to Maemo would be easy, nokia still would have to license it for the new platform/device.

well, the last news concerning maemo on the project site is this:

"Simultaneous with the launch of the wiki, we have started to support
maemo4. Currently cacao, classpath and SWT are tested and work fine.
They have the same features and limitations, as for maemo3. But we hope
to improve the support on maemo4, soon. Since maemo moved to gtk2.10 and
cairo, we have some more options on this platform."

to me, that suggests that even more work will be needed to optimize it for maemo5. granted, the build for chinook might run out of the box ( i haven't read anything from people who got a n900 already, links are welcome ).
if it does run well, there is no need for this option and i will not add it.

though that quote also suggests that there is not much activity any more (this entry is from 2007), and if many people vote maybe that could change and even attract new devs for the project.

very interesting, didn't know about that!

i will add it to the Java SE Proposal:


community or nokia builds Iced Tea
+) true GPL, no binary components
-) no team so far
-) no official advertising

the inclusion of Java is essential to offer a complete development platform to all developers not only C, C + +, Python, etc. ..

From this we can think how to integrate Java in Maemo

I just found something on the Nokia Forums: link.

that seems to be an official statement, is there any point in including the "nokia options" in the brainstorm proposal now, qgil?

MIDP 3.0 is in Proposed Final Draft, so there is no JavaME VM with support yet. Read more here: http://jcp.org/aboutJava/communitypr...271/index.html

Is the guy who has made this statement working for Nokia?

• If you want to use Java to develop for Maemo, then check Jalimo.
• If you want to use Java to run J2SE applications or applets, check for Java SE Embedded, IcedTea or "full" GNU Classpath with a GNU VM.
• If you want to use Java to run J2ME... well, try to do it first on your PC and then do whatever you did on your PC in your Tablet.