• Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.3.0
    • Fix Version/s: None
    • Component/s: Code
    • Labels:
    • Environment:

      Using composer to bring in Log4php on a Drupal system on Linux with a GIT repository controlling code.


      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

      Thanks for considering.


        There are no comments yet on this issue.


          • Assignee:
            adriancottersc adrian cotter
          • Votes:
            0 Vote for this issue
            1 Start watching this issue


            • Created: