sfDoctrinePlugin2 won't work. The plugin name must end with Plugin. I will commit the new plugin system very soon. This new system is based on a "real" PEAR channel on the server and client side. For symfony 1.0, there is a compatibility server side script that emulates the old way of doing things. So 1.0 projects will still work as expected and won't be able to install 1.1 plugins.
Here is how it will work. You install a plugin like this: ./symfony plugin:install sfDoctrinePlugin By default, it looks for a plugin named sfDoctrinePlugin in the plugins.symfony-project.com channel (this channel is the one connected to the wiki). The plugin:install task installs the latest version available for your project symfony version. So let's say you have the following versions available on trac: - sfDoctrinePlugin v. 1.0.4-beta (for symfony 1.1.X) - sfDoctrinePlugin v. 1.0.3-beta (for symfony 1.0.X) - sfDoctrinePlugin v. 1.0.2-stable (for symfony 1.1.X) - sfDoctrinePlugin v. 1.0.1-stable (for symfony 1.0.X) The previous command installs version 1.0.2 (stable and for 1.1.X). To install the latest beta version, use: ./symfony plugin:install sfDoctrinePlugin-beta If you want to force the installation of a particular version: ./symfony plugin:install sfDoctrinePlugin-1.0.2 Now, if you try to install the same plugin in a symfony 1.0 project: ./symfony plugin-install http://plugins.symfony-project.com/sfDoctrinePlugin It installs version 1.0.3. symfony 1.0 always installs the latest version (there no stability check). But it won't install 1.0.4 because of the new server side component. To sum up, the new system reads the symfony dependency versions in the package.xml and acts accordingly. So, you can create a new branch for the sfDoctrinePlugin repository and still be able to maintain the old branch if needed. To ease things, you can also change the major version of the plugin. Version 1.XXX for the sfDoctrinePlugin that works with symfony 1.0 and 2.XXX for the one working with symfony 1.1. I'm also working on a trac macro to output a table with all available versions of a plugin with dependencies and symfony versions. Fabien Matthias N. wrote: > On 20 Sep., 18:05, "Dave Dash" <[EMAIL PROTECTED]> wrote: >> Matthias, >> >> Unfortunately I think the plugins need to end in "Plugin" (there's an easy >> test for this ;) ) >> >> Furthermore, Fabien mentioned something at camp about prefixing plugins with >> out initials versus sf... not sure where that is at. > > I'm afraid I didn't understand what you mean. no more sf prefix for > plugins? Or should one use another one? > >> So I'm a little confused as to the reason for creating a new plugin? Is >> Doctrine 1.0 going to become more or less stable and maybe branch in a new >> direction for future versions? > > Doctrine is on its way to 1.0. The main reason is that the > sfDoctrinePlugin needs a complete rewrite for all new features of > Doctrine and it should work with symfony 1.1. For example the schema > and fixtures support is currently implemented directly in Doctrine - > it also provides possibilities to migrate between database schemas. > And it will probably be no fun to try to support both sf 1.0 and 1.1 > in one plugin. For example we need to create new tasks for the new CLI > system. So the plan is to create a new one using all the good new > features and later backport them step by step to the good old plugin > for sf 1.0. But most people will probably upgrade to sf 1.1 as > soon. ;-) > > Regards, > Matthias > > > >> -d >> >> On 9/20/07, Matthias N. <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >>> Hi, >>> we, Jon Wage and I discussed today to create a new Doctrine plugin >>> that will be symfony 1.1 only with support for the brand new features >>> of Doctrine and symfony as well. >>> I just wondered if it is possible to have the name "sfDoctrinePlugin2" >>> as it is the second version of the plugin - not of Doctrine!? IMHO >>> "sfDoctrine2Plugin" would not reflect what it actually is. >>> I want to create a wiki page for a bit of brainstorming before we >>> start implementing it. >>> Is it possible to have the "2" at the end for the wiki page as well as >>> the plugin name? Or does this not work with the installer or the magic >>> on the website? >>> Regards, >>> Matthias >> -- >> Dave Dash >> 612.670.0621 >> Discover your favorite restaurant: reviewsby.us >> gtalk: dave.dash > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
