If I Install smarty via composer like this:
{
"require": {
"smarty/smarty": "~3.1"
}
}
i get Smarty /tags/v3.1.20/@4891 with the modified directory structure (no
distribution-folder anymore). But the autoload-part in smarty's composer.json
still contains the distribution-folder:
"autoload": {
"classmap": [
"distribution/libs/Smarty.class.php",
"distribution/libs/SmartyBC.class.php",
"distribution/libs/sysplugins/smarty_security.php"
]
},
This causes a RuntimeException:
Could not scan for classes inside
"/Users/matthiaskrauser/www/test/vendor/smarty/smarty/distribution/libs/Smarty.c
lass.php" which does not appear to be a file nor a folder
I cleared the composer-cache before testing this!
Looks like the same issue as
https://code.google.com/p/smarty-php/issues/detail?id=203.
Please: Do not change a released tag to fix this issue. Release a new one
instead!!! Public tags are never ever meant to be changed, even if bug's are
contained.
Original issue reported on code.google.com by matthias...@googlemail.com on 13 Oct 2014 at 8:08
Original issue reported on code.google.com by
matthias...@googlemail.com
on 13 Oct 2014 at 8:08