Changeset 3763 for trunk/doc/src/docbook/developerdoc/plugin_developer.xml
- Timestamp:
- Sep 21, 2007, 2:35:48 PM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/src/docbook/developerdoc/plugin_developer.xml
r3759 r3763 117 117 manifest="MANIFEST.MF" 118 118 > 119 <!--Include this to add required files for auto registration wizard--> 120 <metainf file="./base-plugins.xml"></metainf> 121 <metainf file="./base-configurations.xml"></metainf> 119 122 </jar> 120 123 … … 132 135 <programlisting>Manifest-Version: 1.0 133 136 Class-Path: OtherJar.jar ASecondJar.jar</programlisting> 137 </para> 138 <para> 139 If your plugin should support registration with the auto-installation-wizzard it 140 could be a good idea to add the 141 <sgmltag class="element">metainf</sgmltag> 142 tags. By doing this you don't have to insert any files to the plugin-jar file 143 after it had been created. Place the 144 <filename>base-plugins.xml</filename> 145 and 146 <filename>base-configurations.xml</filename> 147 (if any configurations are shipped with the plugin) in the project root 148 directory before you compile. The files will end up in the jar-file's 149 <filename class="directory">META-INF</filename> 150 . Go to 151 <xref linkend="plugin_developer.organize.autoinstallcompatible" /> 152 to get more information how to create this files. 134 153 </para> 135 154 </sect3> … … 172 191 </para> 173 192 <programlisting><?xml version="1.0" encoding="UTF-8"?> 174 <!DOCTYPE plugins SYSTEM " ../src/core/net/sf/basedb/core/dtd/base-plugins.dtd" >193 <!DOCTYPE plugins SYSTEM "base-plugins.dtd" > 175 194 <plugins jarname="<filename>jarfile.jar</filename>"> 176 195 <pluginclass classname="<classname>se.lu.thep.PluginClass</classname>"> … … 238 257 A required child element in 239 258 <sgmltag class="element">pluginclass</sgmltag> 240 . This should have informationif there are plugin configurations241 that areshipped with the plugin. Setting the value to259 . This should tell if there are plugin configurations 260 shipped with the plugin. Setting the value to 242 261 <emphasis>yes</emphasis> 243 262 will indicate that there are available configurations in the … … 247 266 <para> 248 267 Configurations shipped with a jar-file should be exported with the 249 plugin configuration exporter in BASE. The exported file shouldhave268 plugin configuration exporter in BASE. The exported file must have 250 269 the name 251 270 <filename>base-configurations.xml</filename>
Note: See TracChangeset
for help on using the changeset viewer.