CODEWITHSUNDEEP
jsonsymfonycomposer-php
RdeV
RdeV

Reputation: 173

composer.json in a Symfony bundle

I've created a new Symfony bundle in our local git server which is working nicely. I'm using it in a new Symfony project, the bundle imported into the project using Composer to vendor\Company\AppBundleIt depends on an external bundle so I made a composer.json file in the root of that bundle:

{
  "name": "Company/AppBundle",
  "description": "Application resources",
  "type": "symfony-bundle",
  "license": [
    "proprietary"
  ],
  "require": {
     "jms/metadata": "~1.1"
  }
}

Now I'd expect a composer update to get the jms/metadata package but it doesn't.

I import the Company/AppBundle in the following way:

"repositories": [
    {
        "type": "package",
        "package": {
            "name": "Company/AppBundle",
            "version": "2.1.2",
            "source": {
                "url": "git://github.com/guillaumepotier/parsley.js.git",
                "type": "git",
                "reference": "2.1.2"
            }
        }
    }
],
"require": {
    "Company/AppBundle": "*",
}

composer list --tree does show Company/AppBundle but doesn't list any dependencies under it.

composer validate --with-dependencies Doesn't have any relevant information.

Upvotes: 0

Views: 1752

Answers (1)

alcohol
alcohol

Reputation: 24126

It sounds like you added a composer.json file in vendor/Company/AppBundle. Modifying content in your vendor directory is never recommended. The vendor directory is also not used by composer to determine requirements (even in the case of a path repository, it is still the source that is read from, not the vendor directory).

I also do not understand how you managed to install your Company/AppBundle if it does not have a composer.json already. Can you please elaborate more about the hierarchy of your project/dependencies and which depends on what?

Upvotes: 2

Related Questions