Bug #41418

Manifestpath detection broken, exception in production context

Added by Karsten Dambekalns almost 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Must have
Category:
Package
Start date:
2012-09-27
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
No
Complexity:

Description

In production context class loading fails because the classloader has a wrong map for namespaces. This is caused by getNamespace() doing the wrong thing - because it finds no composer manifest. See screenshot for why.


Files

manifestpath-error.png (419 KB) manifestpath-error.png Karsten Dambekalns, 2012-09-27 13:37

Related issues

Related to TYPO3 Flow Base Distribution - Story #41031: Composer support for packagingResolvedChristian Jul Jensen2012-09-17

Actions
#1

Updated by Gerrit Code Review almost 9 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15115

#2

Updated by Gerrit Code Review almost 9 years ago

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15115

#3

Updated by Gerrit Code Review almost 9 years ago

Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15115

#4

Updated by Gerrit Code Review almost 9 years ago

Patch set 4 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15115

#5

Updated by Gerrit Code Review almost 9 years ago

Patch set 5 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/15115

#6

Updated by Karsten Dambekalns almost 9 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF