Features conflicts when field bases are used by other feature I recently downloaded the Features module and was so glad over how smoothly I now can export functionality from dev to prod. But now when I'm trying to create a second feature I'm getting conflicts because I already used a lot of the same field bases in my first feature.

What can I do to resolve this? Are you not suppose to be able to use the same fields in different features? It doesn't seem right that I should have to define as many fields for "body text" that I have features, or image fields for that matter. Those fields could and should be shared right?

What are my options here?
Say you have two Features, and one field that is used in both Features, then you only need to export the field base ONCE.

This is why I generally have a "controller" Feature that contains field bases, update hooks etc, and then for every other Feature I export the field instance, and then add a dependency on my controller feature.

Basically, you are right - you don't need to export the field bases every time, just export them once and then add dependencies.