Échec de Composer pour le dépôt Gitlab privé

Question

J'ai un nouveau projet pour lequel je veux avoir besoin d'un dépôt Gitlab privé. Les deux dépôts m'appartiennent, donc je peux changer ce que je veux.

El composer.json du projet ressemble :

{
    "name": "thisismyproject",
    "type": "project",
    "minimum-stability": "dev",
    "authors": \[
        {
            "name": "me",
            "email": "me@me.me"
        }
    \],
    "repositories": \[
        {
            "type": "vcs",
            "url": "https://gitlab.com/me/my-wordpress-plugin.git"
        }
    \],
    "require": {
        "composer/installers": "^1.0@dev",
        "me/my-wordpress-plugin": "dev-master"
    },
    "extra": {
        "installer-paths": {
            "wp-content/plugins/{$name}": \[
                "type:wordpress-plugin"
            \]
        }
    },
    "config": {
        "gitlab-token" : {
            "gitlab.com": "thisismysupersecrettoken"
        }
    }
}

El composer.json du dépôt de plugins de wordpress ressemble à ceci :

{
    "name": "WordPress Plugin",
    "description": "lorem",
    "type": "wordpress-plugin",
    "authors": \[
        {
            "name": "me",
            "email": "me@me.de"
        }
    \],
    "require": {},
    "autoload": {
        "psr-4": {
            "SomeNamespace\\\\": "."
        }
    },
    "extra": {
        "branch-alias": {
            "dev-master": "1.0-dev"
        }
    }
}

La sortie de composer update -vvv ressemble :

Downloading https://gitlab.com/api/v4/projects/me%2Fmy-wordpress-plugin
Downloading https://gitlab.com/api/v4/projects/me%2Fmy-wordpress-plugin/repository/branches?per\_page=100
Downloading https://gitlab.com/api/v4/projects/me%2Fmy-wordpress-plugin/repository/files/composer%2Ejson/raw?ref=14
3c1818bfc96dcaa4ee5c26cc0bd379c395491c
Downloading https://gitlab.com/api/v4/projects/me%2Fmy-wordpress-plugin/repository/tags?per\_page=100
Reading composer.json of WordPress Plugin (v1.0.0)
Downloading https://gitlab.com/api/v4/projects/me%2Fmy-wordpress-plugin/repository/files/composer%2Ejson/raw?ref=14
3c1818bfc96dcaa4ee5c26cc0bd379c395491c
Writing /home/vagrant/.cache/composer/repo/gitlab.com/me/my-wordpress-plugin/143c1818bfc96dcaa4ee5c26cc0bd379c39549
1c into cache
Importing tag v1.0.0 (1.0.0.0)
Reading composer.json of WordPress Plugin (master)
Importing branch master (dev-master)
Downloading https://packagist.org/packages.json
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - The requested package me/my-wordpress-plugin could not be found in any version, there may be a typo in the pa
ckage name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see  for more details.

Read  for further common problems.

Des conseils ?

Merci.

Answer 1

Vous recevez l'erreur parce que le nom de votre paquet n'est pas le même.

Pour le corriger, vous devez mettre à jour le nom dans le fichier composer.json de votre plugin WordPress.

{
    "name": "me/my-wordpress-plugin",
    "description": "WordPress Plugin",
    "type": "wordpress-plugin",
    "authors": [
        {
            "name": "me",
            "email": "me@me.de"
        }
    ],
    "require": {},
    "autoload": {
        "psr-4": {
            "SomeNamespace\\": "."
        }
    },
    "extra": {
        "branch-alias": {
            "dev-master": "1.0-dev"
        }
    }
}

Le nom doit correspondre au key dans le require de votre principal composer.json :

"require": {
    "composer/installers": "^1.0@dev",
    "me/my-wordpress-plugin": "dev-master"
},