Yes, I read too quickly your email !

On Mon, Nov 23, 2009 at 3:43 PM, Tom Boutell <[email protected]> wrote:
> Whoops, I meant to delete that incomplete sentence.
>
> What I'm saying here is that devs who are following common examples of
> the right way to start a 1.2 app with no 1.0 dependencies probably
> shouldn't get an error when they run that under the next release,
> since they are trying to follow the recommended path for forwards
> compatibility.
>
> On Mon, Nov 23, 2009 at 6:48 AM, Thomas Rabaix <[email protected]> 
> wrote:
>> The sf1.4 branch will remove all dependencies to 1.0.X series ... so 
>> sfCompat10Plugin does not make any sense with sf1.4. You can use sf1.3 then.
>>
>> On 22 nov. 2009, at 20:36, Tom Boutell wrote:
>>
>>> The project is a new branch of our cmstest project:
>>>
>>> Macintosh-4:cmstest14 boutell$ ./symfony project:upgrade1.4
>>>
>>> http://svn.symfony-project.com/plugins/pkContextCMSPlugin/sandbox/branches/1.4
>>>
>>> I fully expect to hit all sorts of stuff. After all I'm trying to
>>> leapfrog past 1.3 which is presumably more tolerant of 1.2-isms.
>>>
>>> Problem #1:
>>>
>>> Fatal error: Uncaught exception 'InvalidArgumentException' with
>>> message 'The plugin "sfCompat10Plugin" does not exist.' in
>>> /Users/boutell/Sites/cmstest14/lib/vendor/Symfony/lib/config/sfProjectConfiguration.class.php:372
>>>
>>> This is a very, very common setup and prevents the upgrade task from 
>>> running:
>>>
>>> $this->enableAllPluginsExcept(array('sfPropelPlugin', 'sfCompat10Plugin'));
>>>
>>> This is perverse because it punishes folks who are trying to avoid
>>> outdated stuff.
>>>
>>> enableAllPluginsExcept could tolerate disabling plugins that aren't
>>> present anyway (I see little harm in that).
>>>
>>> * * *
>>>
>>> Removed sfCompat10Plugin from that list, moving on:
>>>
>>> Macintosh-4:cmstest14 boutell$ ./symfony project:upgrade1.4
>>>
>>>
>>>  Task "project:upgrade1.4" is not defined.
>>>
>>> Wait, what? Maybe I need to do project:upgrade1.3, as the 1.4
>>> documentation still says (I assumed it was a typo). Let's see if I
>>> can:
>>>
>>> ./symfony | less
>>>
>>> ... Nope. There are no upgrade tasks in 1.4. I have to point
>>> ProjectConfiguration at 1.3 first I guess to do the upgrade before I
>>> can try 1.4. The documentation says nothing about this:
>>>
>>> http://www.symfony-project.org/tutorial/1_4/en/upgrade
>>>
>>> What's the recommended upgrade path? Should I not even be trying to
>>> use 1.4 with an existing project at this point in time?
>>>
>>> More when I get through checking out 1.3 so I can try that instead.
>>>
>>> --
>>> Tom Boutell
>>> P'unk Avenue
>>> 215 755 1330
>>> punkave.com
>>> window.punkave.com
>>>
>>> --
>>>
>>> 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=.
>>>
>>>
>>
>> --
>>
>> 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=.
>>
>>
>>
>
>
>
> --
> Tom Boutell
> P'unk Avenue
> 215 755 1330
> punkave.com
> window.punkave.com
>
> --
>
> 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=.
>
>
>



-- 
Thomas Rabaix
http://rabaix.net

--

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=.


Reply via email to