VersionEye now supports custom repositories for Composer

Yesterday night I pushed a new version online. Up to know we supported only simple composer.json files like this here:

{
  "require": {
    "symfony/symfony": "2.0.7",
    "symfony/doctrine-bundle" : "*",
    "symfony/process" : "2.0.*",
    "symfony/browser-kit" : "!= 2.0.6",
    "symfony/security-bundle" : ">=2.0.7",
    "symfony/locale" : "<=2.0.7",
    "symfony/yaml": "<2.0.8",
    "symfony/http-kernel": ">2.0.6",
    "twig/twig" : ">=1.9.1,<2.0.0",
    "doctrine/common" : ">2.2 , <2.4",
    "symfony/console" : ">=2.0.0, <2.0.10, !=2.0.6"
  }
}

If you refered to a package that is not on packagist.org than we displayed it as unknown. But since yesterday VersionEye supports custom repositories. Here is an example:

{
  "name": "till/wtfdate",
  "description": "A WIP library to provide a somewhat API-compatible replacement for Zend_Date.",
  "license": "BSD-2-Clause",
  "repositories": [
   {
     "type": "package",
     "package": {
       "name": "zendframework/zendframework1-dl",
       "version": "1.12.1",
       "dist": {
         "url": "https://packages.zendframework.com/releases/ZendFramework-1.12.1/ZendFramework-1.12.1-minimal.zip",
         "type": "zip"
       }
     }
   }
 ],
 "autoload": {
   "classmap": [ "src/", "tests/Wtf"]
 },
 "require-dev": {
   "zendframework/zendframework1-dl": "1.12.1"
 }
}

VersionEye now recognises the custom repository and doesn’t display zendframework1-dl as unknown dependency. It displays it as known dependency and as up-to-date.

Let me know how it works for you. I looking forward to your feedback.

http://www.versioneye.com