Enable use as a Composer dependency

[anroots]

Currently, when including the project via Composer as a dependency, it isn't possible to run it: including the Composer autoloader from bin/metrics.php fails, since it is assumed that the project is a root-level project, with its own vendor directory.

To solve that, the following changes would be necessary:

• Tell Composer to move the metrics.php to the Composer vendor/bin dir (optionally, losing the .php extension)
• Rewrite the Composer autoloader inclusion in metrics.php so it would work when the project is included as a dependency

If you'd like, I could try creating a pull request for this.

[UFOMelkor]

Works for me. Did you try the actual version? I use bin as bin-dir …

[anroots]

Ah, yes. My mistake. It works with the latest code.

My problem was that my composer.json read "halleck45/phpmetrics" : "dev-master@dev", but I hadn't lowered my minimum-stability in my root composer.json to dev and that's not something I'm willing to do since it affects all of my dependencies.

I like the tool, I'd like to include it into my CI toolset and it seems to be working reasonably well at the moment... but yeah, I can't include it with Composer (and I don't want to have .phar files in Git, either - damn, I'm picky).

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Removal request for hoa/ruler == 9999999-dev
    - halleck45/phpmetrics v0.0.8 requires hoa/ruler dev-master -> satisfiable by hoa/ruler[dev-master].
    - Installation request for halleck45/phpmetrics 0.0.8 -> satisfiable by halleck45/phpmetrics[v0.0.8].

An article I read this morning suggested this:

To avoid juggling around dev versions it's much better to just tag releases. If you are using a library that has no tagged releases, go and annoy the maintainer until they tag. Do it, now!

I'll keep an eye on the development and try again when a stable release arrives. :)

[Halleck45]

The stable version will come in few days :)

[UFOMelkor]

👍

[maschmann]

👍

[Halleck45]

v1.0.0 released

[anroots]

Excellent! Will try to integrate it to my CI build tomorrow.

Great work!

[anroots]

Problem 1
    - ci-tools dev-develop requires halleck45/phpmetrics ~1.0 -> satisfiable by halleck45/phpmetrics[v1.0.0].
    - ci-tools dev-develop requires halleck45/phpmetrics ~1.0 -> satisfiable by halleck45/phpmetrics[v1.0.0].
    - halleck45/phpmetrics v1.0.0 requires hoa/ruler dev-master -> no matching package found.
    - Installation request for ci-tools dev-develop -> satisfiable by ci-tools[dev-develop].

If I understand correctly, the problem is that hoa/ruler has no tagged releases, hence Composer considers it to be on dev stability, but my minimum-stability is set to RC (I'd like to keep it there).

Two ideas:

• Would adding a @dev flag to hoa/ruler inclusion work to tell Composer it's OK to include the package at dev stability, even though the master says RC? ("hoa/ruler": "dev-master@dev")
• Should I ask Hoa whether they plan to tag a release?

[Halleck45]

Would adding a @dev flag to hoa/ruler inclusion work to tell Composer it's OK to include the package at dev stability, even though the master says RC? ("hoa/ruler": "dev-master@dev")

No, I think that the problem will be the same

Should I ask Hoa whether they plan to tag a release?

Maybe @Hywan can tag Hal/Ruler, but tagging repository is a hard task (in maintenability) and should be a conscious decision.

Another way consists to

• fork Hoa/Ruler
• tagging this fork
• add a repository node in the composer.json file of PhpMetrics

Perhaps there was a better solution....

[Hywan]

Hello from Greece,

We are going to tag all our libraries in few weeks. It will solve your issue :-).

Stay tuned.

[Halleck45]

Hi @Hywan,

That is a good news. Out of curiosity, what strategy will you finally use?

So I flag this issue with the status "waiting". Thank's