when we produce a new build of the j2me client, how will users know...
Summary: j2me versioning. → J2ME Client - versioning.
Good question. I propose the following solution. After the midlet is started (and probably after login too) it looks what version it is itself (by looking into its MANIFEST.MF) and then asks the joey webservice if there is a newer version and what is its url. Then the midlet can do a platform request on the url and exit itself. The user must then install that new midlet and restart the application. Another solution might be that the server also returns the current version on successful login. What do you think?
Status: NEW → ASSIGNED
I already am hosting install version information for the firefox addon on our server, so it isn't a big deal to host something else for the midlet. Let me know the format, and I can host it. It would also be very nice if the build system generated this file. I already copy all of dist to our server, so if the version file was part of this copy, less work for everyone.
Does this mean all available midlets will have the same version? Either we generate some file with infos about the all midlets or take the infos from the JAD file that would be downloaded. The JADs already have this info in the MIDlet-Version property.
i think all midlets should be versioned in sync. At startup or weekly, the midlet checks to see if there is a more recent version of the midlet by fetching a file from a known location that contains a version string.
I will change the build process to create one file called dist/version.txt. This will contain the version of the current build. IMO the server should add a new response header to the answer on logins. This way we need no extra request cycle for this and we check for updates often enough. The last outstanding problem is that you need to make sure to update the version number for all builds you put onto the server. But this is more an organizational problem. What do you think?
yup. all builds will be in lockstep wrt versioning.
I commited the midlet implementation for this now. Important is that the download base url for all JAD files need to be compiled into the MIDlets. This means when you build with the joey.update.url property beind set to http://joey.labs.mozilla.com/app/webroot/ff/ (default) it will always try to download the JAD of the new version from there.
where is this value set Michael?
Joey has been retired. Thanks for participating. http://joey.labs.mozilla.com/
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.