PageRenderTime 223ms CodeModel.GetById 218ms app.highlight 2ms RepoModel.GetById 1ms app.codeStats 0ms

/jEdit/tags/jedit-4-2-pre14/doc/users-guide/plugin-tips.xml

#
XML | 30 lines | 21 code | 6 blank | 3 comment | 0 complexity | 2d1a500da209adad837876287338ae36 MD5 | raw file
 1<!-- jEdit buffer-local properties: -->
 2<!-- :tabSize=1:indentSize=1:noTabs=true: -->
 3<!-- :xml.root=users-guide.xml: -->
 4
 5<chapter id="plugin-tips"><title>Plugin Tips and Techniques</title>
 6
 7<sect1 id="plugin-tips-libraries"><title>Bundling Additional Class Libraries</title>
 8
 9<para>
10  Recall that any class whose name ends with <classname>Plugin.class</classname>
11  is called a plugin core class.
12  JAR files with no plugin core classes are also loaded by jEdit; 
13  the classes they contain are
14  made available to other plugins.  Many plugins that rely on
15  third-party class libraries ship them as separate JAR files.  The libraries
16  will be available inside the jEdit environment but are not part of a general
17  classpath or library collection when running other Java applications.
18</para>
19
20<para>
21  A plugin that bundles extra JAR files must list them in the
22  <filename>plugin.<replaceable>class name</replaceable>.jars</filename>
23  property. See the documentation for the
24  <ulink url="../api/org/gjt/sp/jedit/EditPlugin.html">
25  <classname>EditPlugin</classname></ulink> class for details.
26</para>
27
28</sect1>
29
30</chapter>