erik/kobalt-doc
erik/kobalt-doc
1
0
Fork 0
mirror of https://github.com/ethauvin/kobalt-doc.git synced 2025-04-25 03:57:11 -07:00
Code Releases Activity

Rename plugin.xml -> kobalt-plugin.xml.

Browse source
This commit is contained in:
Cedric Beust 2015-11-16 03:09:31 -08:00
parent c3363183e2
commit 803caaaadd
2 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

8
plug-in-development/index.html
View file

@ -58,7 +58,7 @@
Kobalt plug-ins are usually made of several parts: Kobalt plug-ins are usually made of several parts:
<ul> <ul>
<li><a href="#plugin-xml"><b>plugin.xml</b></a>. A file that describes all the components of your plug-in, such as contributors.</li> <li><a href="#plugin-xml"><b>kobalt-plugin.xml</b></a>. A file that describes all the components of your plug-in, such as contributors.</li>
<li><a href="#directives"><b>Directives</b></a>. Kotlin functions that users of your plug-in can invoke in their build file, such as <code>kotlinProject</code> or <code>dependencies</code>. These functions typically configure some data that your plug-in will later use to perform its functions.</li> <li><a href="#directives"><b>Directives</b></a>. Kotlin functions that users of your plug-in can invoke in their build file, such as <code>kotlinProject</code> or <code>dependencies</code>. These functions typically configure some data that your plug-in will later use to perform its functions.</li>
<li><a href="#tasks"><b>Tasks</b></a>. These tasks are invoked from the command line and ask your plug-ins to perform certain actions.</li> <li><a href="#tasks"><b>Tasks</b></a>. These tasks are invoked from the command line and ask your plug-ins to perform certain actions.</li>
<li><a href="#properties"><b>Properties</b></a>. Plug-ins can export properties and read properties from other plug-ins.</li> <li><a href="#properties"><b>Properties</b></a>. Plug-ins can export properties and read properties from other plug-ins.</li>
@ -70,9 +70,9 @@
and keep reading. and keep reading.
</p> </p>
<h2 class="section" id="plugin-xml">plugin.xml</h2> <h2 class="section" id="kobalt-plugin-xml">kobalt-plugin.xml</h2>
<p> <p>
The <code>plugin.xml</code> file (stored in <code>META-INF</code> in the jar file of your plug-in) is mandatory and describes all the components of your plug-in. At a minimum, The <code>kobalt-plugin.xml</code> file (stored in <code>META-INF</code> in the jar file of your plug-in) is mandatory and describes all the components of your plug-in. At a minimum,
this file will contain the name of your plug-in and the main plug-in class: this file will contain the name of your plug-in and the main plug-in class:
</p> </p>
<pre> <pre>
@ -100,7 +100,7 @@
</p> </p>
<p>In order to make things more concrete, let's take a look at <p>In order to make things more concrete, let's take a look at
<a href=https://github.com/cbeust/kobalt/blob/master/src/main/resources/META-INF/plugin.xml">Kobalt's own <code>plugin.xml</code></a> <a href=https://github.com/cbeust/kobalt/blob/master/src/main/resources/META-INF/kobalt-plugin.xml">Kobalt's own <code>kobalt-plugin.xml</code></a>
and go over it line by line. and go over it line by line.
</p> </p>
<h4>plugins (<a href="https://github.com/cbeust/kobalt/blob/master/src/main/kotlin/com/beust/kobalt/api/IPlugin.kt"><code>IPlugin</code>)</a></h4> <h4>plugins (<a href="https://github.com/cbeust/kobalt/blob/master/src/main/kotlin/com/beust/kobalt/api/IPlugin.kt"><code>IPlugin</code>)</a></h4>

2
ten-minutes/index.html
View file

@ -84,7 +84,7 @@ val project = kotlinProject {
</pre> </pre>
<p> <p>
Next, we need to create our <code>plugin.xml</code> file in the <code>src/main/resources/META-INF</code> directory. Next, we need to create our <code>kobalt-plugin.xml</code> file in the <code>src/main/resources/META-INF</code> directory.
Once there, it will be automatically copied in the right place in our jar file: Once there, it will be automatically copied in the right place in our jar file:
</p> </p>