Skip to content

Commit

Permalink
Laravel 5.2 update
Browse files Browse the repository at this point in the history
  • Loading branch information
@bpocallaghan
bpocallaghan committed Mar 10, 2016
1 parent 79a8a7f commit ad04ad7
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion readme.md
View file
Original file line number Diff line number Diff line change
@@ -1,4 +1,7 @@
# Laravel 5.2 File Generators
# Laravel 5 File Generators

Laravel 5.1, use tag 2.1.3
Laravel 5.2, use tag 2.1.4+

Custom Laravel 5 File Generators with a config file and publishable stubs.
You can add new stubs in the config.
Expand Down

3 comments on commit ad04ad7

@sirsquall
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Man I lose so many time because of you...

I ran a composer update and I had this error message :

php artisan clear-compiled


  [ReflectionException]                             
  Class Illuminate\Support\Composer does not exist  


Script php artisan clear-compiled handling the post-update-cmd event returned with an error


  [RuntimeException]  
  Error Output:

Please use branch instead of tagging the master and saying "Laravel 5.2, use tag 2.1.4" because everyone will ran a composer update and all the people using your package in laravel 5.1 will be ****.

So please create a separated branch 3.0.0 or what you want and like that you can maintain laravel 5.1 the LTS and in the new branch the laravel 5.2.

Thanks
Alcindo

@bpocallaghan
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Alcindo

I am truly sorry about this. I've added a 2.0 and 3.0 branch and removed the 2.14 tag and moved it to 3.0.0 tag.
Please let me know if I messed something up or if this is better / working for you.

Also, please let me know about any changes / stubs I can add that will speed up your workflow or help in any way.

I've recently started to use the AdminLTE skin, and I will definitely add those stubs in as well, and maybe some of my controller / model traits that speed up the basic crud stuff a little.

Again, sorry about the tagging issue.

@sirsquall
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi,

Thanks you for your reactivity, everything is working well now.

Good idea for the AdminLTE skin, I know a lot of people are using this theme.

Alcindo

Please sign in to comment.