It was mainly for things like "this plugin needs you to hook it up to
a database" where we can't reasonably provide a database -- you have
to set up a DB instance and a connection pool with the right name and
then the plugin will install. Or it could be a dependency on a
proprietary driver or product where we can't distribute that product
as a plugin dependency. I can think of a number of cases where there
wouldn't be a way for us to provide a one-size-fits-all dependency.
Thanks,
Aaron
On Dec 12, 2007 6:33 PM, David Jencks <[EMAIL PROTECTED]> wrote:
> Aaron included a prerequisite feature for plugin metadata which is
> supposed to prevent you from installing a plugin if some prerequisite
> plugin is missing. After some thought I can't think of a reason this
> would possibly be useful or more useful than a dependency, where the
> needed plugin is simply installed for you.
>
> I disabled this functionality but forgot to discuss this point, but
> now that Jarek has re-enabled it I think it's time for a discussion.
>
> I do think there is some use for some feature that e.g. prevents
> installing jetty if tomcat is present, but I don't think
> prerequisites implement that in any useful way.
>
> comments?
> thanks
> david jencks
>
>
>
