Feature #41900
Bug #41843: Composer and rename issues (umbrella issue)
Check for duplicate PSR-0 autoload namespaces
| Status: | Accepted | Start date: | 2012-10-12 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Christian Jul Jensen | % Done: | 0% |
|
| Category: | Package | |||
| Target version: | - | |||
| PHP Version: | 5.4 | Complexity: | ||
| Has patch: | No |
Description
Currently, if two packages define the same PSR-0 autoload namespace in their composer.json, it goes unnoticed by the package management.
For example, if someone (let's say, me) just copies a composer manifest from a different package (TYPO3.Flow) and forgets to update the "autoload" part, the new package will end up in a directory "TYPO3.Flow" too. The symptom then is that no Flow classes can be found by the autoloader, because it looks into the other package directory.
While generating PackageStates.php (or somewhere in that area) we should check for duplicate PSR-0 namespaces and issue a warning.
History
#1 Updated by Christian Jul Jensen almost 3 years ago
- Status changed from New to Accepted
- Assigned To set to Christian Jul Jensen
#2 Updated by Karsten Dambekalns over 2 years ago
- Target version changed from 2.0 beta 1 to 2.1
#3 Updated by Robert Lemke about 2 years ago
- Target version deleted (
2.1)