Remove Composer Manager dependency

Hello, Thanks for the feedback.

Composer Manager makes the most logical sense for the module so it will stay a dependency to assist those that are not as much of a developer.

Here is why: Drupal 7 has no support for Composer in core (nothing to run autoload.php). Therefore; composer can only be used in Drupal 7 by either a) hacking core, b) custom module, or c) Composer Manager module. Of those three, Composer Manager is the most logical choice to provide to people installing the module. Without Composer Manager, installation of this module would be difficult to document. Even with Composer Manager, it already is a difficult installation.

If you want the dependency removed, there is nothing in the module code that requires it. You can write a small patch to remove the line from the .info and use drush make.

Lastly, to date this is the only request every received about removing Composer Manager. If there are more people that request this and find this thread then we can start trying to develop some alternatives.

I have websites hosted on Omega8.cc (Aegir) and I couldn't install the library.

Can't I just download and place it in all/libraries and not using the composer_manager module?

Running drush @mysite en -y sendgrid_integration went a long way and finally returned errors.

This is at /admin/config/system/composer-manager:

Composer's install command must be run to generate the autoloader and install the required packages.
Refer to the instructions on the Composer Manager project page for installing packages. 

So now I should go and try to install composer-manager on my whole host instance, which is not easy?!

Right now, the only way to load the module is via Composer Manager. Putting the files in all/libraries will not work as the module isn't built to load those as an option.

I haven't written code for Libraries because I don't use it. I use Composer for my sites any module that uses Libraries I have a private patch to make them work with Composer. Libraries was a great idea at the time, but Composer does dependencies right. I have to maintain PCI-DSS compliance on my sites, composer helps me stay in compliance easier. drush composer-manager update --no-dev and I just updated every library on my website in one simple command.

If someone wants to contribute the code to load the libraries optionally through Libraries I will commit it.

Ok, I was able to fix this going into my website files/composer directory and running "composer update"
(cause I found this: https://github.com/omega8cc/boa/issues/900)

So, if you are on Omega8.cc (Aegir in general I think):

1. drush @yoursite.com en -y composer-manager
2. cd platforms/028/drupal-7.43.2-prod/yoursite.com/files/composer
3. composer update

does the job.

PS: thank you for your fast reply! :)

Awesome! Thanks for giving the steps to fix for Aegir!

+1 on this feature request. I cannot get composer to work on the platform I am using, it seems to be a great tool for developers but a major headache if you just want to quickly implement a module. Please give us the option of just installing a library.

For anyone else who needs to use this module without the composer manager requirement, here is a little patch to remove it from the .info file.

I am +100 for this feature and i can't believe this arrogant behavior of developers like you forcing people into composer. It might be, you love composer and there is nothing against that point but there is a good reason for people not using it. Composer is hugely flawed by design. But its made and loved by a bunch of coke heads who think thier stuff is pure gold. So they will never listen to anyone else outside Composer galaxy. If Composer would be so good as everyone says, why is it that Linux distributions had to FIX IT before shipping. Fedora, Debian and Gentoo patched Composer by them self because Composer people responded to its flaws by standard Composer attitude which you can find all over the Composer community: "CLOSED! WON'T FIX".

Lastly, to date this is the only request every received about removing Composer Manager.

You kidding right? I came to this project, saw composer as dependency and only had a wish for its removal. I've did a quick search at the issue queue and found 2 other removal requests (next to this one) already existing with WON'T FIX.

Having a Drupal 7 project running with some 90 modules build in the last 3 years and just switching to Sendgrid makes me install composer because you say so.

Seems you are passionate about this issue (venture to say hostile), as this is open source please feel free to fork the code. I push everything to Github too.

Even if your module is nice, i will not fork the code as i have already switched back to SMTP. I don't have a problem with using a package manager if it would be implemented in a way that makes it obsolete to have additional managers (one for Drupal, one for Linux etc.) to manage to package manager. We need composer manager to manage composer because its developers acting with "closed won't fix" to request of a proper dependency management.

Hey Brady,
Thanks for the great module! We are using the composer_autoload module which conflicts with composer_manager so we are not able to install the sendgrid integration module either. Any chance we may open the idea of removing the dependency?

Here's a patch to get past the database check if you update the module and run update.php.

@wesjones, You are not using the latest dev code. The dependency was already removed. Closing this as outdated. But I did forget to remove the update 7001 code.

I'm trying to get this module installed. I use Composer, but admittedly I'm not expert at Composer with D7. I first tried to follow the README, installed Composer Manager and ran 'drush composer-manager update --no-dev'. It appeared to pull the dependencies (after I jacked up my PHP memory to 2GB). But I still can't enable the sendgrid_integration module due to the dependency message:

You need to install the SendGrid API wrapper via one of the two methods documented in the README.md of the module. (Currently using SendGrid API Wrapper API Wrapper Library Missing)

I then read through all of the issues relating to Composer. I see you've spent quite a bit of effort on this and I really appreciate that. I'm willing to use whatever approach is suggested, but for some reason I'm stumped.

It sounds like Composer is no longer a hard requirement? If so, I'm not sure how to get this working. I've moved the https://github.com/taz77/sendgrid-php-ng library listed on the sendgrid_integration main page to the Libraries folder (assume that's right?), but no go.

Any advice would be much appreciated. Thanks for making this module available to the Drupal community!

I have the same problem here. Cannot enable Sendgrid Integration although I followed the installation instructions.

Any advice ?

Using 7.x-1.3, I kept getting the message below until I installed and enabled Composer Manager, even though Composer Manager is not listed as a requirement anymore.

You need to install the SendGrid API wrapper via one of the two methods documented in the README.md of the module. (Currently using SendGrid API Wrapper API Wrapper Library Missing)

The message kept coming up even though I had all the dependencies loaded into the sites/all/vendor folder as required by the module (I copied the folder from another project with known working SendGrid integration). As soon as I enabled Composer Manager, SendGrid was able to be enabled.