8000 PhpUnitBridge Warning: Ambiguous class resolution · Issue #18381 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

PhpUnitBridge Warning: Ambiguous class resolution #18381

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

Closed
eventhorizonpl opened this issue Mar 31, 2016 · 8 comments
Closed

PhpUnitBridge Warning: Ambiguous class resolution #18381

eventhorizonpl opened this issue Mar 31, 2016 · 8 comments

Comments

@eventhorizonpl
Copy link

Hi,

I noticed this while running composer install after update to symfony 3.0.4

Warning: Ambiguous class resolution, "Symfony\Bridge\PhpUnit\ClockMock" was found in both "/home/michal/projekty/rentli/vendor/symfony/phpunit-bridge/ClockMock.php" and "/home/michal/projekty/rentli/vendor/symfony/symfony/src/Symfony/Bridge/PhpUnit/ClockMock.php", the first will be used.
Warning: Ambiguous class resolution, "Symfony\Bridge\PhpUnit\DeprecationErrorHandler" was found in both "/home/michal/projekty/rentli/vendor/symfony/phpunit-bridge/DeprecationErrorHandler.php" and "/home/michal/projekty/rentli/vendor/symfony/symfony/src/Symfony/Bridge/PhpUnit/DeprecationErrorHandler.php", the first will be used.
Warning: Ambiguous class resolution, "Symfony\Bridge\PhpUnit\SymfonyTestsListener" was found in both "/home/michal/projekty/rentli/vendor/symfony/phpunit-bridge/SymfonyTestsListener.php" and "/home/michal/projekty/rentli/vendor/symfony/symfony/src/Symfony/Bridge/PhpUnit/SymfonyTestsListener.php", the first will be used.
Warning: Ambiguous class resolution, "Symfony\Bridge\PhpUnit\TextUI\Command" was found in both "/home/michal/projekty/rentli/vendor/symfony/phpunit-bridge/TextUI/Command.php" and "/home/michal/projekty/rentli/vendor/symfony/symfony/src/Symfony/Bridge/PhpUnit/TextUI/Command.php", the first will be used.
Warning: Ambiguous class resolution, "Symfony\Bridge\PhpUnit\TextUI\TestRunner" was found in both "/home/michal/projekty/rentli/vendor/symfony/phpunit-bridge/TextUI/TestRunner.php" and "/home/michal/projekty/rentli/vendor/symfony/symfony/src/Symfony/Bridge/PhpUnit/TextUI/TestRunner.php", the first will be used.

Best regards,
Michal

@stof
Copy link
Member
stof commented Mar 31, 2016

@nicolas-grekas as the bridge is now autoloaded in symfony/symfony too since a recent change, we should list the bridge in replacements too. Otherwise, we should revert the autoloading change you made recently.

@eventhorizonpl
Copy link
Author

The same issue on another project after update from 2.8.3 to 2.8.4.

@nicolas-grekas
Copy link
Member

We should revert and replace by something in autoload-dev

@nicolas-grekas
Copy link
Member

See #18389

fabpot added a commit that referenced this issue Apr 1, 2016
…colas-grekas)

This PR was merged into the 2.7 branch.

Discussion
----------

Exclude Bridge\PhpUnit from composer.json by default

| Q             | A
| ------------- | ---
| Branch?       | 2.7
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #18381, #18272
| License       | MIT
| Doc PR        | -

Commits
-------

4f90495 Exclude Bridge\PhpUnit from composer.json by default
@fabpot fabpot closed this as completed Apr 1, 2016
@MrMitch
Copy link
MrMitch commented Apr 8, 2016

Hi, thank you for taking the time to address that. Do you know in which version of the 2.8 branch this is likely to ship ?

@eventhorizonpl
Copy link
Author

@MrMitch

fabpot merged it into 2.7 branch, so fix will be in next 2.8.5 release.

@MrMitch
Copy link
MrMitch commented Apr 8, 2016

great, thank you very much for your extra quick answer.

@rparsi
Copy link
rparsi commented Apr 16, 2016

@nicolas-grekas I'm using symfony 3.0.4 and getting this warning, is it going to cause problems for writing unit tests? When will symfony 3.0.4 get the fix?
Thanks in advance.

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

No branches or pull requests

8 participants
0