Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UPDATES #190

Open
way5 opened this issue Apr 29, 2018 · 5 comments
Open

UPDATES #190

way5 opened this issue Apr 29, 2018 · 5 comments

Comments

@way5
Copy link

way5 commented Apr 29, 2018

Hello guys!
Just a simple question: Is it abandoned or support is closed?
Thanks

@tedmasterweb
Copy link

Abandoned. The main drawback is that if another plugin uses the same framework you can have conflicts. See some of the author's other repos for more options.

@way5
Copy link
Author

way5 commented Apr 30, 2018

@tedmasterweb what's the future steps? Do you think to start something based on artisan-like / laravel-like or "that's all folks"?

@tedmasterweb
Copy link

You'd have to ask the owner of this repo. I have no intention of doing anything in this direction.

@way5
Copy link
Author

way5 commented May 1, 2018

that's really sad news buddy. That was really good beginning of something useful.
Anyways thanks for all that work you've done.

@superdav42
Copy link

The Jetpack project has developed the Jetpack Autoloader which fixes problem of conflicts when multiple plugins include different versions of composer dependencies. Anyone who wants to continue this project or start something similar should take a look at there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants