Skip to content
Commits on Oct 15, 2011
  1. @fabpot

    updated vendors

    fabpot committed Oct 15, 2011
Commits on Oct 14, 2011
  1. @fabpot

    updated deps

    fabpot committed Oct 15, 2011
Commits on Oct 13, 2011
  1. @fabpot

    merged 2.0

    fabpot committed Oct 13, 2011
  2. @fabpot

    fixed markup in config.php

    fabpot committed Oct 13, 2011
Commits on Oct 9, 2011
  1. @fabpot
Commits on Oct 8, 2011
  1. @fabpot

    merged branch weaverryan/test_client_static (PR #216)

    Commits
    -------
    
    921e203 [DemoBundle] Fixing test client - `createClient()` is a static function
    
    Discussion
    ----------
    
    [DemoBundle] Fixing test client - `createClient()` is a static function
    
    Hey guys!
    
    I think this code is just a little out-dated - back from before the test client was made static.
    
    Thanks!
    fabpot committed Oct 8, 2011
Commits on Oct 7, 2011
  1. @weaverryan
  2. @fabpot

    merged branch weaverryan/bin_vendor_root_dir_specify (PR #214)

    Commits
    -------
    
    8686e87 Explicitly passing the project's root dir to the build_bootstrap.php script
    
    Discussion
    ----------
    
    Bin vendor root dir specify
    
    Hey guys!
    
    Explicitly passing the project's root dir to the build_bootstrap.php script
    
    This takes advantage of a recent change in the SensioDistributionBundle which allows this. A specific situation this addresses is when the `vendor` dir is symlinked, and the build_bootstrap.php script mistakenly places the bootstrap.php.cache in ../app of the vendor dir's real location (instead of actually inside the project).
    
    See: sensiolabs/SensioDistributionBundle#9
    
    Thanks!
    
    ---------------------------------------------------------------------------
    
    by stof at 2011/10/07 11:41:26 -0700
    
    You should use ``escapeshellargs`` for the rootDir too
    
    ---------------------------------------------------------------------------
    
    by stof at 2011/10/07 12:20:37 -0700
    
    #215 does the same fix but with the call to escapeshellargs
    fabpot committed Oct 7, 2011
  3. @weaverryan

    Explicitly passing the project's root dir to the build_bootstrap.php …

    …script
    
    This takes advantage of a recent change in the SensioDistributionBundle which allows this. A specific situation this addresses is when the `vendor` dir is symlinked, and the build_bootstrap.php script mistakenly places the bootstrap.php.cache in ../app of the vendor dir's real location (instead of actually inside the project).
    weaverryan committed Oct 7, 2011
Commits on Oct 6, 2011
  1. @fabpot

    merged branch jcrombez/master (PR #212)

    Commits
    -------
    
    070de68 Message correction to reflect the recent naming change of "parameters.ini" to "parameters.yml".
    
    Discussion
    ----------
    
    Message correction to reflect the recent naming change of "parameters.ini" to "parameters.yml".
    
    Message correction to reflect the recent naming change of "parameters.ini" to "parameters.yml".
    
    Bug fix: yes
    Feature addition: no
    Backwards compatibility break: no
    Symfony2 tests pass: -
    Fixes the following tickets: -
    fabpot committed Oct 6, 2011
  2. @jcrombez

    Message correction to reflect the recent naming change of "parameters…

    ….ini" to "parameters.yml".
    jcrombez committed Oct 6, 2011
Commits on Oct 4, 2011
  1. @fabpot

    merged branch CloudCompany/mkdir_cache_folder (PR #209)

    Commits
    -------
    
    858934a create app/cache folder by default
    
    Discussion
    ----------
    
    create app/cache folder by default
    fabpot committed Oct 4, 2011
  2. @fabpot

    merged branch schmittjoh/patch-2 (PR #211)

    Commits
    -------
    
    0ec0c12 updated version
    
    Discussion
    ----------
    
    updated version
    fabpot committed Oct 4, 2011
  3. @schmittjoh

    updated version

    schmittjoh committed Oct 4, 2011
  4. @fabpot

    updated vendors to dev branches

    fabpot committed Oct 4, 2011
  5. @fabpot

    updated VENDORS for 2.0.4

    fabpot committed Oct 4, 2011
Commits on Oct 3, 2011
  1. @fabpot
Commits on Sep 30, 2011
  1. @fabpot

    updated vendors

    fabpot committed Sep 30, 2011
Commits on Sep 29, 2011
  1. @julesbou
  2. @fabpot
Commits on Sep 28, 2011
  1. @fabpot

    added a commented umask(0000) to simplify permissions setup (should o…

    …nly be used in the dev environment though)
    fabpot committed Sep 28, 2011
  2. @fabpot
  3. @fabpot
Commits on Sep 25, 2011
  1. @fabpot

    updated vendors to dev branches

    fabpot committed Sep 25, 2011
  2. @fabpot

    updated VENDORS for 2.0.3

    fabpot committed Sep 25, 2011
  3. @fabpot

    updated vendors to dev branches

    fabpot committed Sep 25, 2011
  4. @fabpot

    updated VENDORS for 2.0.2

    fabpot committed Sep 25, 2011
Commits on Sep 20, 2011
  1. @fabpot

    merged branch stealth35/add_tok (PR #205)

    Commits
    -------
    
    4e6f7a5 Fix 169 Update requirements : tokenkizer
    
    Discussion
    ----------
    
    Fix #169 Update requirements : tokenkizer
    
    Fix #169
    fabpot committed Sep 20, 2011
  2. @fabpot

    updated vendors

    fabpot committed Sep 20, 2011
  3. @fabpot

    updated AsseticBundle to 1.0.1

    fabpot committed Sep 20, 2011
Commits on Sep 19, 2011
  1. @stealth35
  2. @fabpot

    merged branch lsmith77/vendors_lock (PR #167)

    Commits
    -------
    
    fe13c82 added support to lock vendors as they are currently checked out
    
    Discussion
    ----------
    
    added support to lock vendors as they are currently checked out
    
    ---------------------------------------------------------------------------
    
    by brikou at 2011/07/30 05:46:33 -0700
    
    +1
    
    ---------------------------------------------------------------------------
    
    by lsmith77 at 2011/09/05 10:18:44 -0700
    
    @fabpot: would really be nice to have this merged. seems quite low risk and highly useful.
    
    ---------------------------------------------------------------------------
    
    by jmikola at 2011/09/05 12:37:55 -0700
    
    Reading the diff is a bit confusing, but is this just a new command option to update the deps.lock file without doing anything else? If so, it sounds worthwhile.
    
    Would this help folks that have reported accidentally losing their local changes in vendor directories?
    
    ---------------------------------------------------------------------------
    
    by lsmith77 at 2011/09/05 12:41:54 -0700
    
    yes, all it adds is a new ``bin/vendor lock`` command.
    use case is the following: you manually check out a newer version or branch of a vendor, or you even commit into the vendor. then once you are done you want to lock exactly the version of the code you currently have checked out.
    
    right now you will have to either manually do ``git log`` and copy the hash into ``deps.lock`` or run ``bin/vendor update`` and then revert whatever lines you dont want updated in ``deps.lock`` risking that in case you have uncommitted changes in any of the vendors that those changes will be lost.
    fabpot committed Sep 19, 2011
  3. @fabpot

    updated vendors

    fabpot committed Sep 19, 2011
  4. @fabpot

    merged branch schmittjoh/patch-1 (PR #199)

    Commits
    -------
    
    a65eec7 use the BC branch
    
    Discussion
    ----------
    
    use the BC branch
    
    ---------------------------------------------------------------------------
    
    by fabriceb at 2011/09/14 02:01:37 -0700
    
    The most dangerous BC breaks are those which change the configuration settings (which Johannes just did in JMSSecurityExtraBundle). Because you might update all the dependencies to their correct versions, and still have a major break in your application because of a configuration parameter not in the new format.
    
    I am therefore strongly in favor of fixing all revisions of all bundles in the Symfony standard edition.
    
    ---------------------------------------------------------------------------
    
    by stof at 2011/09/14 05:11:12 -0700
    
    @fabriceb The SE comes with locked version in deps.lock which should be used.
    
    @schmittjoh you need to check the version in deps.lock
    
    ---------------------------------------------------------------------------
    
    by mbadolato at 2011/09/14 09:26:49 -0700
    
    The SE (at least the github download) has deps.lock updates to it that break the distribution. There were changes yesterday (to a few dependancies) and Twig broke, for instance. Also, until yesterdays updates, it was locked at 2.0.0 and not the current 2.0.1 release.
    
    Should the github repository no longer be used for SE downloads, making the packaged download the only real distribution? That's fine if it is, I'm just curious because I track the Git repository and still do merge updates to my project when I see them, to ensure I'm staying current with SE. So, if I need to stop doing that and just wait for packaged release, I can do that.  My question to packaged releases, though, is when update s are done, can we rely on just updating deps and deps.lock, or will we also need to update things in app/ and bin/ etc?
    
    ---------------------------------------------------------------------------
    
    by stof at 2011/09/14 09:43:50 -0700
    
    @mbadolato Use the 2.0 branch of the symfony-standard repo if you want to use the BC version, or keep the released version.
    For 2.0.x releases, the deps and deps.lock should be enough. For 2.1, you will maybe need some changes in the config but this will be documented when it will be released.
    fabpot committed Sep 19, 2011
  5. @fabpot

    merged branch Seldaek/wintest (PR #204)

    Commits
    -------
    
    25846a1 Adjust the way of checking for windows
    
    Discussion
    ----------
    
    Adjust the way of checking for windows
    fabpot committed Sep 19, 2011
Something went wrong with that request. Please try again.