by Darrel » Fri Mar 18, 2005 9:00 am
As a developer, I encountered the same problem with versions of a program for both 710 and 730. The real problem is that MAM (mobile application manager) requires that if the program name, vendor and version all match, it MUST be the same Jar file. Since the i730 needs a different Jar than the i710, the recent distribution is faulty because they both say the same version.
i730 was uploaded first so it set the "proper" jar.
The fix is for Accutracking to repackage the 710 code by chaning the version in Jad file and MANIFEST.MF in the Jar (e.g. from version 1.0 to 1.0.710).
Since the code does not need to be recompiled, only the jar program and a text editor are needed.
As a developer, I encountered the same problem with versions of a program for both 710 and 730. The real problem is that MAM (mobile application manager) requires that if the program name, vendor and version all match, it MUST be the same Jar file. Since the i730 needs a different Jar than the i710, the recent distribution is faulty because they both say the same version.
i730 was uploaded first so it set the "proper" jar.
The fix is for Accutracking to repackage the 710 code by chaning the version in Jad file and MANIFEST.MF in the Jar (e.g. from version 1.0 to 1.0.710).
Since the code does not need to be recompiled, only the jar program and a text editor are needed.