Hope that someone may suggest a solution.

I have a shared development environment - 1 CF server instance. Each developer
has his/her own copy of the application in their respective home directories.
Each directory is a virtual host on the same machine that uses single shared CF
instance.

Here is where the problem is:
The core components reside in CustomTags/cfc directory to allow multiple
applications in different virtual hosts to instantiate the shared components.

I tried setting up a cfc directory in each of the developer's home directories
to be able to make changes to the core components and check them in to CVS.
For those components to be visible I added each developer's path to the
CustomTags path in administrator. While I can make a distinction between
different paths during instantiation by means of using a variable to specify
location of the cfc (i.e. createobject(#cfc_path#.myCompon)), the problem
arises when one component extends another. I cannot use variable in
<cfcomponent extends="#cfc_path#.parentComponent"> - i know that won't work.

Currently I ended up with the mess: I instantiate the first core component in
my dev directory correctly, but that component tries to extend another in a
different developer's directory rather then mine.

I understand that this is a CFC feature, what I am looking for is an
alternative solution to share core components among several developers without
having to separate the environment or run multiple instances of the CF server.

Any feedback is greatly appreciated.

Henry