How do I resolve this conflict between two Feature modules? I have two content types with various menus, views, menus, etc. which I have packaged as two Feature custom modules.  The two content types both use a taxonomy and use several of the same fields in the database.  When I load these Feature modules in a new site, they show conflicts with each other over these common fields and vocabulary and I am not certain what would be the best way to resolve the conflict.

Although the Feature modules are intended to work together, they do not need to both be present on the same site. Each may also work with other different features as well.  They both use the taxonomy and fields for views filtering etc so it makes sense that they each include these components in their Feature definition.  Should I:


Remove the fields and taxonomy from one of the modules, and declare a dependency to the other?  This is not desirable since each can work without the other.
Make two versions of the features, one for independent use, and one for collaborating.
Define the fields and taxonomy as a separate feature?
Ignore the conflict and enable the modules?  (If I do, will they both share the field?)
Another solution?


I have not yet tested this, but will disabling or uninstalling one of the two Features modules remove the fields from the database even though the other module requires it?
Create a third Feature defining the components(*) used by the other two independent Features.

In the other two Features, remove the components which are now claimed by the third Feature, and instead, list the third Feature as a dependency.



(*) In Features for Drupal 7, however, this functionality isn't yet committed — see http://drupal.org/node/1064472, and help review the proposed code there. — This patch has been committed to Features 7.x-2.x.