I made a non-upwards compatible change to Tsugi to move towards refactoring the current monolithic Tsugi code base into separate components. I already factored out the static content (tsugi-static) which is shared between the PHP and Java implementations.<\/p>\n
Now I am moving the code that was formerly under lib\/vendor<\/b> into its own repository and have it included using Composer<\/a> and Packagist<\/a>.<\/p>\n When you do your next “git pull” or check out a fresh copy, you will need to change your config.php<\/b> and replace one line:<\/p>\n <\/p>\n <\/b><\/p>\n If your Tsugi code explicitly includes anything from lib\/vendor\/Tsugi<\/b> (it should not) the fix is to simply remove those includes and allow auto-class loading do work its magic. If you include config.php<\/b> the auto class loader is in effect.<\/p>\n This makes it so we are loading all the Tsugi classes using the auto loader pattern<\/a>. Interestingly this allows me to make use of the Tsugi utility code<\/a> in projects that are not even using LTI.<\/p>\n At this point, I am including the composer.lock<\/b> file and vendor<\/b> folder in the Tsugi GitHub repo<\/a> so that it is a one-stop check out that has the files in their new locations and uses autoloading.<\/p>\nRemove this line:\r\n\r\nrequire_once($dirroot.\"\/lib\/vendor\/Tsugi\/Config\/ConfigInfo.php\");\r\n\r\nAdd this line:\r\n\r\nrequire_once($dirroot.\"\/vendor\/autoload.php\");\r\n<\/pre>\n