felix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r865536 - in /websites/staging/felix/trunk/content: ./ documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html
Date Thu, 13 Jun 2013 10:15:18 GMT
Author: buildbot
Date: Thu Jun 13 10:15:18 2013
New Revision: 865536

Log:
Staging update by buildbot for felix

Modified:
    websites/staging/felix/trunk/content/   (props changed)
    websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html

Propchange: websites/staging/felix/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jun 13 10:15:18 2013
@@ -1 +1 @@
-1492607
+1492609

Modified: websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html
(original)
+++ websites/staging/felix/trunk/content/documentation/subprojects/apache-felix-maven-bundle-plugin-bnd.html
Thu Jun 13 10:15:18 2013
@@ -84,7 +84,7 @@
 <div class="tip" markdown="1"><a href="http://www.aqute.biz/Bnd/Format" class="external-link"
rel="nofollow">A complete list of instructions and their format is available from the BND
website</a></div>
 
 <h1 id="simple-example">Simple Example</h1>
-<p>Rather than going straight to a detailed list of plugin features, we will first
look at a simple example of how to use the plugin to give an immediate flavor. A detailed
"<a href="">how to</a>" will follow.</p>
+<p>Rather than going straight to a detailed list of plugin features, we will first
look at a simple example of how to use the plugin to give an immediate flavor. A detailed
"<a href="#detailed-how-to">how to</a>" will follow.</p>
 <p>Assume that we have a simple bundle project that has a pubic API package an several
implementation packages, such as:</p>
 <div class="codehilite"><pre><span class="n">org</span><span class="p">.</span><span
class="n">foo</span><span class="p">.</span><span class="n">myproject</span><span
class="p">.</span><span class="n">api</span>
 <span class="n">org</span><span class="p">.</span><span class="n">foo</span><span
class="p">.</span><span class="n">myproject</span><span class="p">.</span><span
class="n">impl1</span>
@@ -113,9 +113,9 @@
 </pre></div>
 
 
-<p>The <code>&lt;Export-Package&gt;</code> and <code>&lt;Private-Package&gt;</code>
instructions tell the plugin about the contents of the resulting bundle JAR file. The <code>&lt;Export-Package&gt;</code>
instruction tells the plugin which of the available packages to copy into the bundle <em>and</em>
export, while the <code>&lt;Private-Package&gt;</code> instruction indicates
which of the available packages to copy into the bundle <em>but not</em> export.
If the two sets overlap, as they do in the case, then the export takes precedence. Since we
did not specify any values for any other bundle manifest headers, they will assume default
values which are described <a href="">below</a>. One specific behavior to highlight
is that the plugin generates the <code>Import-Package</code> bundle manifest header
based on the contents of the bundle, which means that you generally do not ever need to explicitly
specify it yourself. That's it.</p>
+<p>The <code>&lt;Export-Package&gt;</code> and <code>&lt;Private-Package&gt;</code>
instructions tell the plugin about the contents of the resulting bundle JAR file. The <code>&lt;Export-Package&gt;</code>
instruction tells the plugin which of the available packages to copy into the bundle <em>and</em>
export, while the <code>&lt;Private-Package&gt;</code> instruction indicates
which of the available packages to copy into the bundle <em>but not</em> export.
If the two sets overlap, as they do in the case, then the export takes precedence. Since we
did not specify any values for any other bundle manifest headers, they will assume default
values which are described <a href="#default-behavior">below</a>. One specific
behavior to highlight is that the plugin generates the <code>Import-Package</code>
bundle manifest header based on the contents of the bundle, which means that you generally
do not ever need to explicitly specify it yourself. That's it.</p>
 <h1 id="features">Features</h1>
-<p>The BND library underlying the plugin defines instructions to direct its behavior.
For this Maven plugin, these instructions are issued in the plugin configuration section of
the POM file, as was illustrated <a href="">above</a>. BND recognizes three types
of instructions:</p>
+<p>The BND library underlying the plugin defines instructions to direct its behavior.
For this Maven plugin, these instructions are issued in the plugin configuration section of
the POM file, as was illustrated <a href="#simple-example">above</a>. BND recognizes
three types of instructions:</p>
 <ol>
 <li><em>Manifest headers</em> - Any instruction that starts with a capital
letter will appear in the resulting bundle's manifest file; the value for the header will
either be copied, augmented, or generated by BND depending on the instruction.</li>
 <li><em>Variables</em> - Any instruction starting with a lowercase letter
is assumed to be a variable in the form of a name-value pair, such as <code>version=3.0</code>,
that can be used for property substitution, but is not copied to the manifest.</li>
@@ -862,9 +862,9 @@ As shown in the above example, you could
 <li>obr.xml (file given by the user to add properties not found by Bindex) must be
correct, because the plug-in does not check its syntax.</li>
 </ol>
 <h1 id="feedback">Feedback</h1>
-<p>Subscribe to the Felix users mailing list by sending a message to <a href="">users-subscribe@felix.apache.org</a>;
after subscribing, email questions or feedback to [users@felix.apache.org|mailto:users@felix.apache.org].</p>
+<p>Subscribe to the Felix users mailing list by sending a message to <a href="mailto:users-subscribe@felix.apache.org">users-subscribe@felix.apache.org</a>;
after subscribing, email questions or feedback to <a href="mailto:users@felix.apache.org">users@felix.apache.org</a>.</p>
       <div class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
-        Rev. 1492607 by mcculls on Thu, 13 Jun 2013 10:04:08 +0000
+        Rev. 1492609 by mcculls on Thu, 13 Jun 2013 10:15:10 +0000
       </div>
       <div class="trademarkFooter"> 
         Apache Felix, Felix, Apache, the Apache feather logo, and the Apache Felix project



Mime
View raw message