Development

Symfony11Plugins (diff)

You must first sign up to be able to contribute.

Changes from Version 1 of Symfony11Plugins

Show
Ignore:
Author:
fabien (IP: 62.240.242.149)
Timestamp:
02/28/08 11:49:50 (10 years ago)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Symfony11Plugins

    v0 v1  
     1= Plugins for symfony 1.1 = 
     2 
     3symfony 1.1 plugin management has been rewritten from scratch. The symfony plugin system is now based on a "real" PEAR channel. 
     4 
     5The symfony 1.1 PEAR channel is `plugins.symfony-project.org` (with an alias of `symfony-plugins`). 
     6 
     7== Plugin installation == 
     8 
     9To install a plugin, you can use the `plugin:install` task: 
     10 
     11{{{ 
     12./symfony plugin:install sfGuardPlugin 
     13}}} 
     14 
     15To have all the available options and syntax, use the help task: 
     16 
     17{{{ 
     18./symfony help plugin:install 
     19}}} 
     20 
     21The book has been updated with the latest information on how to install plugins (http://www.symfony-project.org/book/1_1/17-Extending-Symfony#Installing%20a%20Plug-In) 
     22 
     23== Plugin authors == 
     24 
     25If you host your plugins on the `symfony-project.com` website and want to upgrade your plugins to work with symfony 1.1, here are some tips: 
     26 
     27  * If you use the symfony subversion repository, change the main SVN directory structure like this: 
     28 
     29    {{{ 
     30      myPlugin/branches/1.0/   <- Plugin compatible with symfony 1.0 
     31      myPlugin/branches/1.1/   <- Plugin compatible with symfony 1.1 
     32      myPlugin/tags/ 
     33      myPlugin/trunk/ 
     34    }}} 
     35 
     36    This allow to support both symfony 1.0 and symfony 1.1. 
     37 
     38  * For symfony 1.1, you need to update the `package.xml` file: 
     39 
     40     * change the channel to plugins.symfony-plugins.org 
     41     * change the symfony compatibility to 1.1 (and exclude 1.2) 
     42 
     43When releasing a new version of a plugin, attach the PEAR package to the plugin page as before. The symfony CLI will do the "right" thing based on the symfony version you have in your current project (based on the symfony dependency you have configured in your `package.xml`).