-
Notifications
You must be signed in to change notification settings - Fork 72
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't add doctrine/dbal as direct dependency #1846
Comments
Doctrine is no runtime dependeny. It is just added because of the fact, that the exception implementation in NC21 is not complete and we have to directly catch the DBAL Exceptions. Without this dependency the tests fail. Since DBAL is not shipped with the package, there is no conflict. DBAL will be dropped, once NC21 support is dropped. |
Since DBAL is a dev dependency, composer should be called with the |
Lines 42 to 45 in 0af2118
I also see a vendor/doctrine/dbal in https://github.com/nextcloud/polls/releases/download/v3.0.0/polls.tar.gz |
Signed-off-by: dartcafe <github@dartcafe.de>
The moment when you open the |
Thanks for taking care 馃憤 |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Hi 馃憢
Thanks for your nice app 馃憤 I run into the following error today.
What is going wrong? What did you observe?
Polls 3.0.0 has doctrine/dbal 3.1 as direct dependency. As doctrine/dbal 3.0 is included in Nextcloud this might lead to conflicts. Please don't require doctrine/dbal in composer.json.
A possible workaround could be: nextcloud/news#636. It depends a bit on your use case. replace in composer.json is a bit hacky.
Example: A stack trace caused by another app showing the doctrine from polls/vendor is used.
Information about your polls installation
Polls version: 3.0.0
Information about your Instance of Nextcloud
Nextcloud version: 21.0.3
The text was updated successfully, but these errors were encountered: