Not really. Plug-in decomposition is much like package decomposition.
It's really up to you if you want a whole bunch of views in one plug-in
verses each in its own. Certainly making finer grained decomposition
allows for finer grained reuse, but that's assuming that dependencies
don't kick in to drag in other plug-ins indirectly...
Craig wrote:
Are there any guidelines to help determine when a view should be
contained in its own plugin vs. one plugin containing multiple views?