I inherited a year-old flex/air app that uses air 2.0.
I change the descriptor to 2.6 and I can run it almost error-free.
The problem is that the old <version> is
yes, it is a weird version, but this is the version that is out there now.
I have to update <version> to <versionNumber> for it to work with 2.6.
Now, I cannot make a
<versionNumber>v0.1001.1024</versionNumber> (no letters allowed, no more then 3 digits number)
I can make
for exmaple, but it recognizes v0.1001.1024 as the newer version, meaning that there is no way to update this app to all the current users.
If you move to 2.6, you have to conform to the new requirements. Why did
you move? Maybe you don't need to.
Since I am now working on this inherited project, I would like to work with an up-to-date library ( air 2.6 ). Is this, in your opinion, an unnecessary added difficulty?
If it ain't broke, don't fix it. If you want to upgrade, you will have to
upgrade various parts of the project as well.