I made an ebuild for the J2ME Wireless Toolkit from sun. I will also upload the license for this. Please note: I used dev-java/sun-jdk-1.3 instead of virtual/jdk-1.3 because I had problems testing it with the blackdown-jdk. ---- The Java 2 Platform, Micro Edition (J2ME) Wireless Toolkit is a state-of-the-art toolbox for developing wireless applications that are based on J2ME's Connected Limited Device Configuration (CLDC) and Mobile Information Device Profile (MIDP), and designed to run on cell phones, mainstream personal digital assistants, and other small mobile devices. The toolkit includes the emulation environments, performance optimization and tuning features, documentation, and examples that developers need to bring efficient and successful wireless applications to market quickly. ---- Reproducible: Always Steps to Reproduce:
Created attachment 39465 [details] sun-j2me-1.0.4.01.ebuild
Created attachment 39466 [details] sun-bcla-j2me (License File)
The ebuild works fine for me :) I just wish there was an ebuild for the latest version - 2.2
Created attachment 45328 [details] sun-j2me-2.2.ebuild >I just wish there was an ebuild for the latest version - 2.2 Oh, I did not notice that it came out :) Here is the new Version and a diff to the old one.
Created attachment 45329 [details, diff] sun-j2me-2.2.ebuild.patch
Thanks!! :)
*** Bug 73378 has been marked as a duplicate of this bug. ***
Hi :) Unfortunatelly there is something wrong, I don't know if it's because of the e-build or because the installer itself... When I've installed the e-build and as non-root user tried running some programs on emulator I got a warning message like this: "Warning: Failed to initialize WMA message routing support" and there also was something about Bluetooth. The emulator would come up but I couldn't do a thing and soon it'd crash. When I used root account there waren't any problems, no warnings whatsoever. It seemed like a problem with file rights. After some searching I've found this site: http://rzr.online.fr/docs/java/linux.htm In the troubleshooting section, more specifically "SDK modes", there's a suggestion to use: chmod -R a+rwX /opt/sun-j2me-2.2 chmod -R a+rwX /opt/sun-j2me-2.2/appdb And it helped - I can run the emulator and no warnings appear. Is this really the right thing to do or just a hack?? Giving every user and group all rights makes me feel unsafe... ;) One more thing. Is it possible for the ebuild to make it to the portage? It would really be great :) Regards, Crocodil
Update: > Please note: I used dev-java/sun-jdk-1.3 instead > of virtual/jdk-1.3 because I had problems testing > it with the blackdown-jdk. The j2me works fine with dev-java/blackdown-jdk-1.4.2.01-r2.
Created attachment 65460 [details] sun-j2me-2.2.ebuild Fixed download page.
Created attachment 65461 [details] digest-sun-j2me-2.2 Added digest file
Created attachment 65462 [details] Manifest added Manifest
The ebuild works now. Please include in portage very soon.
You don't need to attach the digest and Manifest files to bugs. Users/devs can generate them with ebuild digest. I have a couple of comments about your ebuild: ( jar xf install.zip >/dev/null && rm install.zip ) || die ( foobar ) means that the command is executed in a subshell, which is probably not what you want here. I also think that we should install a symlink to ktoolbar to /opt/bin so that it is in $PATH. DEPEND=">=dev-java/sun-jdk-1.4.2" Why the jdk? We don't need a jdk to install this thing. You can use unzip instead of jar to unzip the files. Your src_install does not work: chmod: cannot access `/var/tmp/portage/sun-j2me-bin-2.2/image//opt/sun-j2me-bin-2.2/bin/*.jar': No such file or directory I recommend installing everything first with doins instead of installing the bins with doexe and then other stuff with cp -r. After installing you can make the files which need to be executable, executable using fperms. And the final issue: There are packed jars included in the jars installed: for example the activation.jar and mail.jar. These should come from the packages which provide these. See http://gentoo-wiki.com/Gentoo_Java_Policy The purpose of this list was not to make you feel bad but to help you make better ebuilds in the future should you choose to do so. After these issues are solved and I can't find anything else wrong I can commit this to the official tree. Thanks for the work so far and keep it up. If you have any questions I can be reached by email or at #gentoo-java@freenode.
Created attachment 65477 [details] sun-j2me-2.2.ebuild Thanks for the feedback. So many rules :-) I tried and incorporated as much as possible. I also added two use flags. PS: I am just trying to fix this ebuild. I did not write the original version. PPS: Please change the subject to reflect the correct version of the ebuild.
(In reply to comment #15) > Thanks for the feedback. So many rules :-) I tried and incorporated as much as > possible. I also added two use flags. Java ebuild java have a lot of things that you just have to know. So in the beginning writing them is a long a process of trial and error with a lot of questions. > PS: I am just trying to fix this ebuild. I did not write the original version. Sorry about that, but the feedback applies as much to all the writers. > PPS: Please change the subject to reflect the correct version of the ebuild. done
http://gentooexperimental.org/svn/java/gentoo-java-experimental/dev-java/sun-j2me-bin/ Added this to the experimental tree. At least two things need to be fixed before this can go official: 1. jars should be installed using java-pkg_dojar 2. it should not install the packed jars 3. Some of the included jars should probably be packaged separately for example the lib/jsrXXX.jar files
Any updates on this? It's been idle for a *long* time
In portage.
env variable WTK_HOME is not set after installation. I dont know, if it is "bug" or not, but it could be nice, if ebuild sets WTK_HOME variable to "/opt/sun-j2me-bin-2.5.2.01/" after installation. It will make my maven project work out of box. pom.xml contains "<systemPath>${env.WTK_HOME}/lib/jsr179.jar</systemPath>" and some similar things...
