I have just checked in the first pass of the standard build file for plugins (see SharedCode). It would be nice to enable EmptyPlugin with a build file, as an example, but this plugin is checked into the core. I could always get someone to check in the build file to the EmptyPlugin area, but that's a real pain for me, and for the CoreTeam, from a maintenance perspective.

It would be sensible if the EmptyPlugin were a plugin like any other. I can't see why it isn't. It's documented there, after all. The product build can still wrap this plugin, same as it does for SpreadSheetPlugin etc. It should be in the plugins CVS repository. The same is true of DefaultPlugin and InterwikiPlugin.

A second issue, not so critical, is that the build process depends on SharedCode (TWiki::Plugins::Build, to be precise). So a build.pl checked into the core, and the core built without the shared code, would not work for the end user.

A third issue is that I have been using POD for documentation, and I'd like to be able to use the PERLDOC tag to extract and present that documentation on twiki.org, preferably working from the topic in CVS. But it doesn't work (see SharedCode). Can anyone offer assistance?

-- CrawfordCurrie - 22 Apr 2004