While this might be overkill for your needs, I've used it in the past
to maintain plugins retrieved via svn:externals. It's called Piston
(http://piston.rubyforge.org/), and it allows you to keep a local copy
committed to your own repository, but you can still update from the
upstream repository r
Thomas Rabaix wrote:
> Hello,
>
> I hope you are going to keep the feature !
>
> 1. That help to keep the code clean (Imagine a checkout process in one
> single file ...)
> 2. easy to find the file in eclipse alt+shift+r is your friend
> (textmate offer the same feature...)
> 3. easy way to avoi
Hello,
I hope you are going to keep the feature !
1. That help to keep the code clean (Imagine a checkout process in one
single file ...)
2. easy to find the file in eclipse alt+shift+r is your friend
(textmate offer the same feature...)
3. easy way to avoid errors when working with other devs.
All recent commits are to prepare the introduction of the
sfConfiguration classes. Not everything is quite ready yet for commit.
I hope to commit a first version (without plugin support) soon.
Fabien
--
Fabien Potencier
Sensio CEO - symfony lead developer
http://www.sensiolabs.com/
http://www.
Fabien POTENCIER wrote:
> Hi all,
>
> The symfony 1.1 release comes along nicely but I still have 2
> major/blocking problems which need to be fixed before 1.1-beta1 and I
> have no simple solution:
>
> * Plugins are unable to register routes (#2408)
> * It's not possible to connect listen
