Item13744: Document that EmptyPlugin is documentation only, and cannot be enabled.
Priority: Low
Current State: Closed
Released In: 2.0.2
Target Release: patch
Applies To: Extension
Component: EmptyPlugin
Branches: master
The
EmptyPlugin somehow made it into the release tar ball.
~#tar -tf Foswiki-2.0.1.tgz | grep Empty [15:39]
Foswiki-2.0.1/data/Sandbox/PluginTestEmptyPlugin.txt
Foswiki-2.0.1/data/System/EmptyPlugin.txt
Foswiki-2.0.1/lib/Foswiki/Plugins/EmptyPlugin/
Foswiki-2.0.1/lib/Foswiki/Plugins/EmptyPlugin/Config.spec
Foswiki-2.0.1/lib/Foswiki/Plugins/EmptyPlugin.pm
I could not find the script to actually build a release tarball (would be nice to add that to the repository), and could therefore not fix it directly for future use.
--
MaikGlatki - 23 Sep 2015
The
EmptyPlugin is considered part of our release documentation. That's where all the handler calls are documented. See
System.PerlDoc
It needs to remain part of the release. Is there a problem with including it in the build?
The release process is documented in
BuildingARelease It needs
BuildContrib installed along with some other tools and builds from a git checkout. Not all the pieces to build are included in the tarball.
--
Main.GeorgeClark - 23 Sep 2015 - 16:36
Hi,
Thank you for linking to the build process. I noticed perceived the existance of the
EmptyPlugin as an error, because the pm exists, but it can not be enabled, which makes it unique in the release.
# ./tools/configure -save -noprompt -set "{Plugins}{Enabled}{EmptyPlugin}"="1"
#### ERROR: {Plugins}{Enabled}{EmptyPlugin} was not found in any Config.spec
Really more unexpected behaviour than an error.
--
Main.MaikGlatki - 24 Sep 2015 - 07:09
Updated the
EmptyPlugin documentation topic to state that this plugin cannot be enabled. Also added a link to the PerlDoc page to get the plugin API documentation.
--
Main.GeorgeClark - 24 Sep 2015 - 19:52