Possible [Bug] Workbench Package

[raftalks]

I have fresh installation of L4 beta.
Created a workbench package.
Applied composer update to the package.
Registered the Package Service Provider in App/Config file.
Refreshed home page and got this error.

ReflectionException: Class translator does not exist
in /Users/raf/Sites/hbt2013/L4/app/vendor/laravel/framework/src/Illuminate/Container/Container.php line 274
at ReflectionClass->__construct('translator') in /Users/raf/Sites/hbt2013/L4/app/vendor/laravel/framework/src/Illuminate/Container/Container.php line 274
at Container->build('translator', array()) in /Users/raf/Sites/hbt2013/L4/app/vendor/laravel/framework/src/Illuminate/Container/Container.php line 218
at Container->make('translator', array()) in /Users/raf/Sites/hbt2013/L4/app/vendor/laravel/framework/src/Illuminate/Foundation/Application.php line 261
at Application->make('translator') in /Users/raf/Sites/hbt2013/L4/app/vendor/laravel/framework/src/Illuminate/Container/Container.php line 401
at Container->offsetGet('translator') in /Users/raf/Sites/hbt2013/L4/app/vendor/laravel/framework/src/Illuminate/Support/ServiceProvider.php line 77
at ServiceProvider->package('raftalks/assets') in /Users/raf/Sites/hbt2013/L4/app/workbench/raftalks/assets/src/Raftalks/Assets/AssetsServiceProvider.php line 21
at AssetsServiceProvider->register() in /Users/raf/Sites/hbt2013/L4/app/vendor/laravel/framework/src/Illuminate/Foundation/Application.php line 230
at Application->register(object(AssetsServiceProvider)) in /Users/raf/Sites/hbt2013/L4/app/vendor/laravel/framework/src/Illuminate/Foundation/ProviderRepository.php line 67
at ProviderRepository->load(object(Application), array('Illuminate\Foundation\Providers\ArtisanServiceProvider', 'Illuminate\Auth\AuthServiceProvider', 'Illuminate\Cache\CacheServiceProvider', 'Illuminate\Foundation\Providers\CommandCreatorServiceProvider', 'Illuminate\Foundation\Providers\ComposerServiceProvider', 'Illuminate\Routing\ControllerServiceProvider', 'Illuminate\Cookie\CookieServiceProvider', 'Illuminate\Database\DatabaseServiceProvider', 'Illuminate\Encryption\EncryptionServiceProvider', 'Illuminate\Filesystem\FilesystemServiceProvider', 'Illuminate\Hashing\HashServiceProvider', 'Illuminate\Log\LogServiceProvider', 'Illuminate\Mail\MailServiceProvider', 'Illuminate\Database\MigrationServiceProvider', 'Illuminate\Pagination\PaginationServiceProvider', 'Illuminate\Foundation\Providers\PublisherServiceProvider', 'Illuminate\Redis\RedisServiceProvider', 'Illuminate\Database\SeedServiceProvider', 'Illuminate\Foundation\Providers\ServerServiceProvider', 'Illuminate\Session\SessionServiceProvider', 'Illuminate\Foundation\Providers\TinkerServiceProvider', 'Illuminate\Translation\TranslationServiceProvider', 'Illuminate\Validation\ValidationServiceProvider', 'Illuminate\View\ViewServiceProvider', 'Illuminate\Workbench\WorkbenchServiceProvider', 'Raftalks\Assets\AssetsServiceProvider')) in /Users/raf/Sites/hbt2013/L4/app/vendor/laravel/framework/src/Illuminate/Foundation/start.php line 184
at require('/Users/raf/Sites/hbt2013/L4/app/vendor/laravel/framework/src/Illuminate/Foundation/start.php') in /Users/raf/Sites/hbt2013/L4/app/start.php line 59
at require_once('/Users/raf/Sites/hbt2013/L4/app/start.php') in /Users/raf/Sites/hbt2013/L4/app/public/index.php line 53

I think this is happening because the translator is trying to load the language files from the lang directory of the package when it is empty.

When I removed the package lang directory which gives a temporary solution. I am not sure but I think this is the problem.

[flaviozantut]

I'm having the same problem.

[raftalks]

I am assuming the Translation package of illuminate needs some adjustment to solve this problem.

[taylorotwell]

OK, the problem is I need to make the package call from the boot method and not the register method. The issue you're running into is the TranslationServiceProvider hasn't been registered yet.

[taylorotwell]

Fixed.

[jasonlewis]

Digging this up again @taylorotwell... What would you suggest people do if they need configuration available during the register process? Because you can't bootstrap a package (just the lang side of it anyway) from the register() method should people be registering the service within the boot() if they need configuration. Or should they just use $this->app['config']->package() to do the config side manually in the register() method if they need to.

Cheers.

[franzliedke]

I'm confused, Jason. Shouldn't the config provider be registered before all those service providers?

[raftalks]

@jasonlewis I see you have a point and I like to to say that I am using boot method as suggested by Taylor for now but using $this->app['config']->package() sounds good to me.