The metadata file of an apex class/trigger which is retrieved via Migration tool does not have the packageVersions fields.
Last updated 2013-10-03 ·Reference W-1728580 ·Reported By 10 users
The metadata file of an apex class/trigger which is retrieved via Migration tool does not have the packageVersions fields even if the class/trigger has dependencies to some packages.
steps to replicate
1. install a managed package
2. create an apex class/trigger which has references to classes/triggers included in the installed package.
3. retrieve it using Migration Tool
You'll see that there is no packageVersions field in the retrieved manifest file.
There is no workaround
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.