i am working on an Ace2 addon (i.e. it embeds libraries from Ace2). assuming it is somehow relevant, this addon is Aloft (i have taken it over and am maintaining it;
http://www.wowinterface.com/download...AloftBeta.html)
i have it working on the WoW PTR (i.e. WoW v3.0.2), using a version of the Ace2 libraries from the WoWAce SVN that i assume are currently being "ported" to WoW v3.0.2.
now i am trying to regression test it on a production realm (i.e. WoW 2.4.3), where i have Ace2 addons installed that are using older versions of the Ace2 libraries. i assume my users will be in the same situation: they will have Ace2 addons using these older versions of the libraries.
i am getting what i expect are version conflicts, in various libraries. all of them take a form *like* the following (which we have seen before):
AceOO-2.0-79634 (Aloft):734: AceComm-2.0: AceComm-2.0 requires AceEvent-2.0
AceComm-2.0-79554 (Aloft):2339: in main chunk
|
i assume this arises because AceEvent-2.0 is running in Aloft in a different (newer) version than it is in some other addon (in this case, specifically the production version of "Lib: Ace2", installed from WoWAce as an external), and the version(s) of AceOO-2.0 and/or AceComm-2.0 running in Aloft is detecting this. if i turn off that other mod (disable the external Ace2), and just run my development version of Aloft (with its newer libraries), the error goes away.
is there some way i can protect my users from this sort of confusion? or should i create a WotLK-only release of Aloft for people to use for a few weeks on the PTR/etc?
actually, i think i am inclined to just document this problem for my users and move on (the libraries seem compatible on WoW 2.4.3, they are just noisy at load time, and we only have a few weeks left until WotLK is released, and WoW at large has a patch)?
thanks for any advice you can offer.
Threaded Mode
