-
Notifications
You must be signed in to change notification settings - Fork 694
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
Valet seems to conflict with phing #199
Comments
Yeah we need to do some namespacing of some things. |
I found that the
instead of
with However, I'm a noob with all those namespace, facade things, so I'm not sure if that would be the right thing to do here or not. Please advise. |
I think we should revisit this a bit. So the classes are namespaced now, and it is the facades that cause the issue. Should all the facades be prefixed with Valet. for example |
Would be great if we could get an update on this, still having the same issue |
Lots of global composer stuff conflicts, best solution is to use this instead: |
Ah cool, thanks for that @adamwathan |
That is the key @adamwathan. Thanks! |
I don't really know why, but I had
phing/phing
installed as a global composer package, and as soon as I addlaravel/valet
, I get this.I'm not sure what happens at this point, so I will just create this issue here. I will try to go back to it to see if I can find a possible fix or not 😃.
The text was updated successfully, but these errors were encountered: