Vincent Massol wrote:
Do you mean physically package them, ie. add the dependent plugins to your
plugin's jar?
That would certainly solve issues of plugins not working together and having
to maintain runtime compatible versions.
The cons would be:
- increased disk space (doesn't really matter)
- unability for users to benefit from new features of a dependent plugin.
They would have to wait for a new version of the main plugin to benefit from
them.
No, it is really just a way to reuse existing plugins. I still don't
think plugins can be able to talk to each other without us getting into
the m1 mess.
Probably best to track the discussion on the users list, everything
should be in there.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
