Quote:
Originally Posted by JustAMan
Hmm, what if we make separate 5.0.3 branch that would contain only changes from 5.0.0, and change bundling so it would first get resources for 5.0.0, pack 5.0.0 .tar.gz, then take changes for 5.0.3, pack them to another .tar.gz and so on. That way we would have several .jar/whatever files for each locale numbered by framework version.
The script that is inside install.bin should install the one that is related to current firmware version.
|
Framework localization JAR built from 5.0.0 resources will work just fine on 5.0.3 (as in
diba's case) and vice-versa. This is not an assumption, it is proved by the way in which Java handles resources. Unified JAR could be built from 5.0.3 resources (which are superset of 5.0.0 resources). This is why
ixtab proposes "backporting", i. e. updating resources from 5.0.0 with new resources from 5.0.3 and living with it further. So there is no need for managing of multiple JARs. At least, now.
Besides, I like idea about placing resources from different firmware versions in separate Git branches. This way 5.0.3 could be branched from 5.0.0. It is appealing for me somehow, though I can't say for sure, why... I'll try to consider it carefully.