adrian cotter created LOG4PHP-232:
-------------------------------------
Summary: Git File in composer build
Key: LOG4PHP-232
URL: https://issues.apache.org/jira/browse/LOG4PHP-232
Project: Log4php
Issue Type: Bug
Components: Code
Affects Versions: 2.3.0
Environment: Using composer to bring in Log4php on a Drupal system on
Linux with a GIT repository controlling code.
Reporter: adrian cotter
Priority: Minor
I have a Drupal site using a couple of modules (fb_instant_articles and amp)
that make use of composer. One of the libraries that composer downloads for
these modules is log4php.
The other factor in this is that I manage my code through GIT, and have a
typical dev-stage-prod setup.
When log4php is downloaded by composer there is a .git file that is included in
the library. This basically means that my GIT repository will ignore this
directory -- and so files won't be added to my repository, and thus won't be
passed across to stage or prod. I figured this out after much pain and
suffering, banging of head on keyboard :)
Is there a way that the composer build could exclude this git file? It would
save the likely problem that I will have of re-figuring out this problem
whenever log4php is updated.
Someone suggested I open a ticket here. If your interested in more of the gory
details, they are here on drupal.org
https://www.drupal.org/node/2756677
Thanks for considering.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
