Answers.Body: <p>There's no documentation because it's not really something you would normally do. I admit I don't know how joomla works - in the download file it looks like it might end up in com_civicrm/admin/civicrm? You're looking for a file named <code>composer.json</code>. Then using the command line in that same folder, you'd type <code>composer require guzzlehttp/guzzle:'^7'</code></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-08-09T14:15:11.440Z
Answers.Text: Thanks for answering here as well :-) The correct folder is /administrator/components/com_civicrm/civicrm, and there is indeed a composer.json file in that directory.  I just wanted to confirm that running composer at this point would not screw up the civicrm installation in any unexpected ways.  I guess the best process would be to backup the site and give it a try.
Answers.UserDisplayName: minbori
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-08-09T15:00:52.180Z
Answers.Text: Backup is always good. The command would only affect that folder and subfolders.
Answers.UserDisplayName: Demerit
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2022-08-09T12:59:04.530Z
Answers.LastActivityDate: 2022-08-09T12:59:04.530Z
Answers.UserDisplayName: Demerit
Body: <p>I have an extension version conflict problem on my Joomla site, for which the recommended solution is to change the civicrm dependencies via composer (<a href="https://civicrm.stackexchange.com/questions/42419/guzzle-conflict-between-civicrm-and-community-builder-joomla/42420">Guzzle conflict between CiviCRM and Community Builder (Joomla)?</a>).</p>
  <p>However, this CiviCRM was installed via the Joomla plugin system, and has never been managed by composer.  So essentially, I don't know how to implement the solution :-)</p>
  <p>Composer is installed on the server where CiviCRM resides.  Is it possible to set up composer to manage the Civicrm instance after-the-fact, so I can change these dependencies?  I can't find any documentation on how to do this (all the documentation I'm finding re: CiviCRM and composer are for Drupal).</p>
  <p>Help appreciated, thanks.</p>
  
Tags: <joomla><composer>
Title: is it possible to use composer with a Joomla-installed CiviCRM instance?
ThreadText: # is it possible to use composer with a Joomla-installed CiviCRM instance?
  
  (Asked by: username_0 on 2022-08-09)
  
  I have an extension version conflict problem on my Joomla site, for which the recommended solution is to change the civicrm dependencies via composer ([Guzzle conflict between CiviCRM and Community Builder (Joomla)?](https://civicrm.stackexchange.com/questions/42419/guzzle-conflict-between-civicrm-and-community-builder-joomla/42420)).
  
  However, this CiviCRM was installed via the Joomla plugin system, and has never been managed by composer. So essentially, I don't know how to implement the solution :-)
  
  Composer is installed on the server where CiviCRM resides. Is it possible to set up composer to manage the Civicrm instance after-the-fact, so I can change these dependencies? I can't find any documentation on how to do this (all the documentation I'm finding re: CiviCRM and composer are for Drupal).
  
  Help appreciated, thanks.
  
  **Tags:** joomla, composer
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2022-08-09. Score: 0 | Accepted answer
  
  There's no documentation because it's not really something you would normally do. I admit I don't know how joomla works - in the download file it looks like it might end up in com\_civicrm/admin/civicrm? You're looking for a file named `composer.json`. Then using the command line in that same folder, you'd type `composer require guzzlehttp/guzzle:'^7'`
  
  > **Comments:**
  > **username_0**: Thanks for answering here as well :-) The correct folder is /administrator/components/com_civicrm/civicrm, and there is indeed a composer.json file in that directory.  I just wanted to confirm that running composer at this point would not screw up the civicrm installation in any unexpected ways.  I guess the best process would be to backup the site and give it a try.  
  > **username_1**: Backup is always good. The command would only affect that folder and subfolders.  
  
  ---
  
  