Thorsten Scherler wrote:
...
We have to start a howTo about the forrest dispatcher view
implementation
(view/viewHelper plugins) because now we have docu in both plugins but
to start with views you need *both* plugins installed.
Then this is a plugin dependency. There should be no plugin dependencies. They will cause a maintenance nightmare for both Forrest and its users.
We need to find a way of removing this dependency. I'm still not going to get my teeth into this plugin until after 0.7 is out, so I have no suggestions as to how to remove this particular dependency yet. (some docs will certainly help in understanding this).
Of course, at some point I know I'll have to give up on this point, but as I have said before, I'll hold out as long as I can.
When the time comes for me to give in then we need to define a way of automatically handling those dependencies, it cannot be left to the user to maintain those dependencies. If they want to use a plugin, they should only need to specify one parameter in their properties file.
If this is the first case that really *has* to have a dependency between plugins then we should look at implementing something like features in Eclipse. Features define collections of plugins that are required to provide a certain feature set. The dependencies between plugins are managed within the feature definition so the user simply defines the feature they want and Eclipse (Forrest for us of course) installs all relevant plugins.
Ross
