Bug #62900

Extensions will not be installed into "typo3conf/ext" if no "typo3-ter"-namespaced package is set as a dependency

Added by most wanted about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Start date:
2014-11-13
Due date:
% Done:

100%

Estimated time:

Description

Using a composer.json without any "typo3-ter"-namespaced package as a dependency does not install packages of type "typo3-cms-extension" into folder "typo3conf/ext" but into folder "vendor".

{
    "repositories": [
        {
            "type": "composer",
            "url": "http://composer.typo3.org/" 
        }
    ],
    "require": {
        "typo3/cms": "6.2.*",
        "fab/media": "dev-master" 
    }
}

this works as expected:

{
    "repositories": [
        {
            "type": "composer",
            "url": "http://composer.typo3.org/" 
        }
    ],
    "require": {
        "typo3/cms": "6.2.*",
        "typo3-ter/news": "*",
        "fab/media": "dev-master" 
    }
}
#1

Updated by most wanted about 7 years ago

FYI: the media package is retrieved from packagist:

https://packagist.org/packages/fab/media

#2

Updated by Lars Malach about 7 years ago

The namespace "typo3-ter" doesn't matter..

Your extension "fab/media" gets installed before "typo3/cms-composer-installers" is available, because Git-Branches (dev-master) have a higher priority than version numbers.

To use a Git-Branch in your composer.json, please add this requirement to your extension composer.json:

    "require": {
        "typo3/cms-core": "*" 
    }

#3

Updated by Lars Malach about 7 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF