[FLOW3-general] using libraries via composer
Thomas Mammitzsch
thomas at visualworx.de
Wed Nov 28 17:09:09 CET 2012
Hi Cedric,
ok, good hint with the leading slash. Looks like that now:
use \Guzzle\Http\Client;
But doesnt work here. Still get the "Class 'Guzzle\Http\Client' not
found" error. Yes, im in development context and delete the content of
Data/Temporary every time before i try to debug/run the controller.
I dont get what im doing wrong if you have a working setup with guzzle.
regards, Thomas
On 28.11.2012 16:54, Cedric Ziel wrote:
> Hi Thomas,
>
> In your Controller, you should use Guzzle with leading backslash \Guzzle\Http.. Otherwise, it would be required on the relative Namespace-not in all cases, but enough. I installed guzzle in a product as well (for Geocode) - no confusion there.
>
> I assume u are in Development context and cleaned all existing temporary files, as the process of recompiling doesn't always work well..?
>
> Regards,
> Cedric
>
>
>
> Thomas Mammitzsch <thomas at visualworx.de> schrieb:
>
>> Hi Cedric,
>>
>> i removed the autoload.php from the Packages/Libraries Folder but had
>> no
>> success. It still complains about Class 'PHPUnit_Framework_TestCase'
>> not
>> found. But only for guzzle tests and symfony/event-dispatcher
>> (dependency of guzzle).
>> If i delete the tests folder in both libraries, i get no errors, but
>> that breaks composers status of the libs (composer.phar update detects
>> the missing files and complains).
>> Also guzzle is not available in my command controller -> "Class
>> 'Guzzle\Http\Client' not found in ..." no matter if i keep or remove
>> the
>> Libraries/autoload.php.
>> Something weird with autoloading is going on there...although i must
>> admit that i don't completely understand how that works.
>>
>> regards, Thomas
>>
More information about the FLOW3-general
mailing list