Hi Juan Pablo, One of the things I have considered proposing I'll go ahead and propose. I'm as seems typical lately rather overcommitted so I've not been able to review what's going on with the new APIs but I had the thought that it might be a good idea to actually support, at least for some period of time, **two** plugin APIs, the old and the new. This would enable existing wikis to continue to use older plugins that may have not or may never get updated, whilst still moving forward with newer versions of JSPWiki.
The only difference between the old and new plugin APIs may simply be its own package signature and the package signatures of the respective dependencies (e.g., replacing WikiEngine with its API, etc.). As the author of a lot of plugins, I'd still like to be able to upgrade to the newer versions of JSPWiki for production sites, and upgrade my plugins as time permits. There are likely a lot of private plugins developed for personal or professional sites (that we never hear about) whose developers are either too busy or otherwise unavailable for updating them, and it'd be a shame to force those sites to either abandon what might be essential plugins or never upgrade. Cheers, Murray ........................................................................... Murray Altheim <murray18 at altheim dot com> = = === http://www.altheim.com/murray/ === === = = === In the evening The rice leaves in the garden Rustle in the autumn wind That blows through my reed hut. -- Minamoto no Tsunenobu
