-
-
Notifications
You must be signed in to change notification settings - Fork 319
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
Reliance on PEAR packages despite being removed from PEAR itself #1370
Comments
Hi @paul-gene! Phing 2.x is still available through our (deprecated) channel. Phing 3.x (main branch) is only installable through composer, and the various tasks will be updated to reflect that. There may be error messages that still reference PEAR though (we'll fix them when we see them). |
So to clarify, v3 will not require any PEAR packages for additional tasks such as the GIT related ones? |
Any PEAR packages that we require will be pulled in through Composer, or packaged into the .phar file. |
@siad007 I think I got rid of the mentions of PEAR that need to be removed, can you do a quick double-check? Thanks. |
LGTM |
I have installed Phing via Composer, but tasks such as GitCheckout require PEAR packages to be installed, despite Phing being removed from PEAR.
Are you planning to address this, so no additional PEAR packages are required?
The text was updated successfully, but these errors were encountered: