Bug #37895
Packagemanager::ImportPackage doesn't use package specific Package class
Status:
Closed
Priority:
Could have
Assignee:
-
Category:
-
Target version:
Start date:
2012-06-11
Due date:
% Done:
0%
Estimated time:
PHP Version:
Has patch:
No
Complexity:
Description
The importPackage initiates the standard Package class and not the Package specific one.
I'm not sure if there could be a reason for this. Also it might not be an issue, since it would be loaded correctly on the next run.
Slightly related: I came across this while looking in to composer support, and that would have to make the package specific Package.php optional anyway.
Updated by Karsten Dambekalns about 8 years ago
- Status changed from New to Closed
- Target version set to 2.0
Method no longer exists.