This is likely due to the fact that sfFinder, by default, ignores
symlinks.  I have had similar problems getting symfony to find class
files in libraries which I tried to symlink into my project.  See this
ticket for more information:

http://trac.symfony-project.com/ticket/2164

I'm not positive that symfony propel-build-all uses sfFinder to find
its schema, but it seems likely.

David

On Sun, Feb 24, 2008 at 2:38 PM, naholyr <[EMAIL PROTECTED]> wrote:
>
>  Have you tried to "ls -l" the folder ? See if the link is broken or
>  something else...
>
>
>
>  On 18 fév, 10:25, Kostas Papadimitriou <[EMAIL PROTECTED]> wrote:
>  > cd /stuff/workspace/project1/plugins
>  > ln -s /stuff/workspace/global_plugins/sfGuardPlugin sfGuardPlugin
>  >
>  > stuff mount:
>  > /dev/hda5 on /stuff type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096)
>  > so there are no permission issues
>  >
>  > naholyr wrote:
>  > > How do you make your symbolic link ? (give the exact command you
>  > > typed, and from where you typed it)
>  >
>  > > On 17 fév, 13:45, Kostas Papadimitriou <[EMAIL PROTECTED]> wrote:
>  >
>  > >> I want to share a plugin which includes some schema definitions to
>  > >> several projects by creating a symbolic link of the plugin to each
>  > >> project plugins folder.
>  >
>  > >> When i execute symfony propel-build-all the schema.yml inside the
>  > >> symlinked plugin folder don't get parsed, instead when i make a copy of
>  > >> the folder it does.
>  >
>  > >> Any help on how to make this work ?
>  >
>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to