Active
Project:
Composer Vendor
Version:
7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
22 Mar 2013 at 12:40 UTC
Updated:
5 Feb 2017 at 22:49 UTC
Jump to comment: Most recent
Hello.
Just an FYI, I have likely duplicated efforts in the Composer Manager module. I found Composer and Composer Autoload before submitting my module, but I somehow missed this one. Anyways, I wanted to point you to it as it seems there are some issues in this module's queue that Composer Manager is attacking, and in the spirit of open source and collaboration I wanted to reach out to you.
Thanks,
Chris
Comments
Comment #1
_wdm_ commentedHello,
I was going to build most of the functionality that you have already done. I'll be looking at using Composer Manager before I extend this one any more.
I would be happy to merge into your project and close this one but I have no idea how and if that is possible, have you got any ideas?
Regards
Will
Comment #2
cpliakas commentedHi Will.
Thanks for being open to this, and I am really sorry for stepping on your toes here. Clearly you started this effort first, I just did a bad job a surveying the landscape before moving forward.
Let's try to figure out where the delta is and see if we can reconcile the differences so that the best of both worlds is in one place.
Thanks again,
Chris
Comment #3
donquixote commentedEven I wanted to start a module for this, and then got stuck choosing a module name.
I wish you the best with these efforts!
I think the important part is to agree on a convention for where to put the composer libraries, and how modules can declare their dependencies.
Comment #4
summit commentedHi, Is this module integrated in Composer_manager?
I do not see a autoload.php anywhere on D7?
greetings, Martijn