作曲家：循环依赖中的版本冲突

Question

First of all, I know this setup is stupid but this is what we're stuck with 🤷‍♂️

We build websites with our company framework. The website contains some classes that the framework directly accesses. This means we have a circular dependency. This was not a problem until now.

These are slimmer versions of our composer.json s:

Framework :

The framework just defines some other

{
    "name": "company/framework",
    "type": "library",
    "require": {
        ...
    }
}

Website :

{
    "name": "company/website",
    "require": {
        "company/framework": "^4.3",
        ...
    }
}

Very simple, framework is a dependency of website .

Now, I'm trying to setup a CI server with static analysis for the framework . As mentioned, the framework requires some files in the website for static analysis to succeed.

The new company/framework/composer.json file looks like this:

{
    "name": "company/framework",
    "type": "library",
    "require": {
        "company/website": "^4.3",
        ...
    }
}

This works fine when testing a tagged framework version. Whenever we're in a develop branch Composer will fail since website requires a stable ^4.3 version of the framework but this is a develop branch.

Is there any way I can work around this?

Answer 1

Extract the classes that are needed to test the framework into a separate package.

Framework requires that package.

Website requires that package. And requires Framework (which also requires that package).

Voila, you transformed a circular dependency into a linear graph.

Add semantic versioning to this approach, and you will never have serious problems - or spot them pretty soon.