[ErrorException] Unable to find deploy strategy for module: no known mapping

[yellowmamba]

Hi,

I am running into this problem when installing AW_blog extension. I want to manage this plugin myself, so I downloaded it as a zip from http://packages.firegento.com/. In the package, it contains a package.xml file, which should be found by the installer according to your readme file.But this error occurs, so symlink cannot be done. Here's the installing process:

-> composer install
Loading composer repositories with package information
Installing dependencies (including require-dev)
  - Installing magento-hackathon/magento-composer-installer (1.3.1)
    Loading from cache

 time for voting about the future of the #magento #composer installer.
 https://github.com/magento-hackathon/magento-composer-installer/blob/discussion-master/Milestone/2/index.md
 For the case you don't vote, I will ignore your problems till iam finished with the resulting release.
  - Installing plugins/aw_blog (v1.3.1)
    Cloning 64019641e4c488237a11e6b36bf36ad1d4c21f69

  [ErrorException]
  Unable to find deploy strategy for module: no known mapping

Do you have any idea? Thanks!

[yellowmamba]

Now I have to manually make a modman file to map files to Magento directories. But it'd be good if the packaged package.xml could be utilised, as manually creating modman is really tedious.

Cheers!

[Flyingmana]

Thank you for reporting.

you have a special edge case here, as you try to use it outside of the firegento repository. As you sure noticed, there is no composer.json inside the zip, but we provide this informations via the repository.

"1.3.1": { "name": "connect20/AW_Blog", "version": "1.3.1", "version_normalized": "1.3.1.0", "dist": { "type": "tar", "url": "http://connect20.magentocommerce.com/community/AW_Blog/1.3.1/AW_Blog-1.3.1.tgz", "reference": null, "shasum": null }, "require": { "magento-hackathon/magento-composer-installer": "*" }, "type": "magento-module", "extra": { "package-xml": "package.xml" }, "license": [ "EULA" ], "authors": [ { "name": "AW_Core_Team", "email": "no-reply@aheadworks.com" } ], "description": "Blog for Magento. Shows posts with comments. Comments can be auto approved or moderated by admin. Categories. Plus much more." }

the important part here is "type": "magento-module", "extra": { "package-xml": "package.xml" },

as it points where to find the package.xml

Does this resolve your use case?

[yellowmamba]

Thanks for that. I didn't try it as I now use modman instead now and downloaded the zip from aHeadWorks website which doesn't have a package.xml file in it. But thanks for hinting on using package-xml entry, didn't know that!

[yellowmamba]

Yes, I added package-xml and it worked. Thanks!

[andkirby]

Hey guys, is there any updates about modman file usage?.. I won't use package.xml.

[andkirby]

as manually creating modman is really tedious

By the way, you may try use mine simple generator. https://github.com/andkirby/modman-generator

[daim2k5]

why you don't use composer? @andkirby as @Flyingmana mention it's a edge case :-/

[andkirby]

Sorry, my fault - one of required modules didn't have modman file. Composer for what? I use Composer. I'm using modman to make deploy mapping. Is this way wrong? :)

[Flyingmana]

@andkirby please open a new issue with some more details to reproduce. The name of the package you want to install, the version of this package and the version of composer and the version of the magento composer installer you use.