blob: 7f7bb11874e459083cd7e8dd26152ea01990a504 [file] [log] [blame]
Karl Paulsf87ac142007-07-06 22:36:17 +00001<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
2<html><head><title>Apache Felix</title>
3
4
5
6
7 <link rel="stylesheet" href="maven-bundle-plugin-bnd_files/site.css" type="text/css" media="all">
8 <link rel="stylesheet" href="maven-bundle-plugin-bnd_files/print.html" type="text/css" media="print">
9 <meta http-equiv="Content-Type" content="text/html;charset=UTF-8"></head><body>
10 <div class="title">
11 <img alt="Logo" src="maven-bundle-plugin-bnd_files/apache-felix-small.png" align="right">
12 </div>
13 <div class="menu">
14 <ul>
15 <li><a href="http://cwiki.apache.org/FELIX/index.html">home</a></li>
16 <li><a href="http://cwiki.apache.org/FELIX/news.html">news</a></li>
17 <li><a href="http://cwiki.apache.org/FELIX/status.html">status</a></li>
18 <li><a href="http://cwiki.apache.org/FELIX/license.html">license</a></li>
19 <li><a href="http://cwiki.apache.org/FELIX/downloads.html">downloads</a></li>
20 <li><a href="http://cwiki.apache.org/FELIX/documentation.html">documentation</a></li>
21 <li><a href="http://cwiki.apache.org/FELIX/committers.html">committers</a></li>
22 <li><a href="http://cwiki.apache.org/FELIX/mailinglists.html">mailing lists</a></li>
23 <li><a href="http://cwiki.apache.org/FELIX/faq.html">faq</a></li>
24 <li><a href="http://cwiki.apache.org/FELIX/roadmap.html">roadmap</a></li>
25 <li><a href="http://cwiki.apache.org/FELIX/sourcecode.html">source code</a></li>
26 <li><a href="http://cwiki.apache.org/FELIX/codingstandards.html">coding standards</a></li>
27 <li><a href="http://cwiki.apache.org/FELIX/issuetracking.html">issue tracking</a></li>
28 <li><a href="http://cwiki.apache.org/FELIX/dependencies.html">dependencies</a></li>
29 </ul>
30 </div>
31 <div class="main">
32<h1><a name="MavenBundlePlugin(BND)-BundlePluginforMaven"></a>Bundle Plugin for Maven</h1>
33
34<p>This plugin for Maven 2 is based on the <span class="nobr"><a href="http://www.aqute.biz/Code/Bnd" title="Visit page outside Confluence" rel="nofollow">BND<sup><img class="rendericon" src="maven-bundle-plugin-bnd_files/linkext7.gif" alt="" align="absmiddle" border="0" height="7" width="7"></sup></a></span>
35tool from Peter Kriens. The way BND works is by treating your project
36as a big collection of classes (e.g., project code, dependencies, and
37the class path). The way you create a bundle with BND is to tell it the
38content of the bundle's JAR file as a subset of the available classes.
39This plugin wraps BND to make it work specifically with the Maven 2
40project structure and to provide it with reasonable default behavior
41for Maven 2 projects.</p>
42
43<p><a name="MavenBundlePlugin(BND)-simpleexample"></a></p>
44
45<h1><a name="MavenBundlePlugin(BND)-SimpleExample"></a>Simple Example</h1>
46
47<p>Rather than going straight to a detailed list of plugin features, we
48will first look at a simple example of how to use the plugin to give an
49immediate flavor. A detailed "<a href="#MavenBundlePlugin%2528BND%2529-howto" title="how-to on Maven Bundle Plugin (BND)">how to</a>" will follow.</p>
50
51<p>Assume that we have a simple bundle project that has a pubic API package an several implementation packages, such as:</p>
52<div class="preformatted"><div class="preformattedContent">
53<pre>org.foo.myproject.api
54org.foo.myproject.impl1
55org.foo.myproject.impl2
56...
57</pre>
58</div></div>
59<p>If we also assume that we have a bundle activator in one of the implementation packages, then the <tt>&lt;plugins&gt;</tt> section of the POM file for this bundle project would look like this:</p>
60<div class="preformatted"><div class="preformattedContent">
61<pre>...
62&lt;plugins&gt;
63 &lt;plugin&gt;
64 &lt;groupId&gt;org.apache.felix&lt;/groupId&gt;
65 &lt;artifactId&gt;maven-bundle-plugin&lt;/artifactId&gt;
66 &lt;extensions&gt;true&lt;/extensions&gt;
67 &lt;configuration&gt;
68 &lt;instructions&gt;
69 &lt;Export-Package&gt;org.foo.myproject.api&lt;/Export-Package&gt;
70 &lt;Private-Package&gt;org.foo.myproject.*&lt;/Private-Package&gt;
71 &lt;Bundle-Activator&gt;org.foo.myproject.impl1.Activator&lt;/Bundle-Activator&gt;
72 &lt;/instructions&gt;
73 &lt;/configuration&gt;
74 &lt;/plugin&gt;
75&lt;/plugins&gt;
76...
77</pre>
78</div></div>
79<p>The <tt>&lt;Export-Package&gt;</tt> and <tt>&lt;Private-Package&gt;</tt> instructions tell the plugin about the contents of the resulting bundle JAR file. The <tt>&lt;Export-Package&gt;</tt> instruction tells the plugin which of the available packages to copy into the bundle <b>and</b> export, while the <tt>&lt;Private-Package&gt;</tt> instruction indicates which of the available packages to copy into the bundle <b>but not</b>
80export. If the two sets overlap, as they do in the case, then the
81export takes precedence. Since we did not specify any values for any
82other bundle manifest headers, they will assume default values which
83are described <a href="#MavenBundlePlugin%2528BND%2529-defaultbehavior" title="default-behavior on Maven Bundle Plugin (BND)">below</a>. One specific behavior to highlight is that the plugin generates the <tt>Import-Package</tt>
84bundle manifest header based on the contents of the bundle, which means
85that you generally do not ever need to explicitly specify it yourself.
86That's it.</p>
87
88<h1><a name="MavenBundlePlugin(BND)-Features"></a>Features</h1>
89
90<p>The BND library underlying the plugin defines instructions to direct
91its behavior. For this Maven plugin, these instructions are issued in
92the plugin configuration section of the POM file, as was illustrated <a href="#MavenBundlePlugin%2528BND%2529-simpleexample" title="simple-example on Maven Bundle Plugin (BND)">above</a>. BND recognizes three types of instructions:</p>
93<ol>
94 <li><em>Manifest headers</em> - Any instruction that starts with
95a capital letter will appear in the resulting bundle's manifest file;
96the value for the header will either be copied, augmented, or generated
97by BND depending on the instruction.</li>
98 <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 <tt>version=3.0</tt>, that can be used for property substitution, but is not copied to the manifest.</li>
99 <li><em>Directives</em>
100- Any instruction starting with a '-' character is considered to be a
101directive that informs BND to perform some special processing and is
102not copied to the manifest.</li>
103</ol>
104
105
106<p>The remainder of this section covers the most important aspects of BND's instructions; for complete details refer to the <span class="nobr"><a href="http://www.aqute.biz/Code/Bnd" title="Visit page outside Confluence" rel="nofollow">BND documentation<sup><img class="rendericon" src="maven-bundle-plugin-bnd_files/linkext7.gif" alt="" align="absmiddle" border="0" height="7" width="7"></sup></a></span>.</p>
107
108<p><a name="MavenBundlePlugin(BND)-instructions"></a></p>
109
110<h2><a name="MavenBundlePlugin(BND)-Instructions"></a>Instructions</h2>
111
112
113<h3><a name="MavenBundlePlugin(BND)-{{&lt;ExportPackage&gt;}}"></a><tt>&lt;Export-Package&gt;</tt></h3>
114
115<p>The <tt>&lt;Export-Package&gt;</tt> instruction is a list of
116packages for the bundle to export. These packages are copied into the
117resulting bundle JAR file from the available classes (i.e., project
118classes, dependencies, and class path); thus, it is possible to include
119classes into your bundle that are not associated with source files in
120your project. <tt>&lt;Export-Package&gt;</tt> can be specified with
121package patterns using the '*' wildcard. Also, it is possible to
122exclude packages using negation by starting the package pattern with
123'!'. Thus, non-negated patterns indicate which of the available
124packages to include in the bundle, whereas negated patterns indicate
125which should not be included in the bundle.</p>
126
127<p>The list of package patterns is ordered and earlier patterns are applied before later patterns. For example, if you specify "<tt>org.foo.*,!org.foo.impl</tt>" the second pattern has no effect since all <tt>org.foo</tt> packages have already been selected by the first pattern. Instead, you should specify "<tt>!org.foo.impl,org.foo.*</tt>", which will export all <tt>org.foo</tt> packages except <tt>org.foo.impl</tt>.</p>
128
129<p>Following standard OSGi R4 syntax, package patterns can include both
130directives and attributes, which will be copied appropriately into the
131generated Export-Package manifest header. Besides explicitly listing
132package version attributes, BND will also determine package versions by
133examining the source JAR file or from <tt>packageinfo</tt> files in the package directory.</p>
134
135<h3><a name="MavenBundlePlugin(BND)-{{&lt;PrivatePackage&gt;}}"></a><tt>&lt;Private-Package&gt;</tt></h3>
136
137<p>The <tt>&lt;Private-Package&gt;</tt> instruction is similar in every way to the <tt>&lt;Export-Package&gt;</tt> instruction, except for the fact that these packages will <b>not</b>
138be exported by the bundle. If a package is selected by both the export
139and private package headers, then the export takes precedence.</p>
140
141<h3><a name="MavenBundlePlugin(BND)-{{&lt;IncludeResource&gt;}}"></a><tt>&lt;Include-Resource&gt;</tt></h3>
142
143<p>The <tt>&lt;Include-Resource&gt;</tt> instruction is a list of
144arbitrary resources that should be copied into the bundle JAR file. The
145specified resources are declared as clauses that can have the following
146forms:</p>
147<div class="preformatted"><div class="preformattedContent">
148<pre>clause ::= assignment | inline | simple
149assignment ::= PATH '=' PATH
150simple ::= PATH
151inline ::= '@' PATH
152</pre>
153</div></div>
154<p>For the <tt>&lt;Include-Resource&gt;</tt> instruction, actual file paths are relative to the <tt>pom.xml</tt>, while file copy destinations are relative to the root of the resulting bundle JAR file. In the case of <tt>assignment</tt> or <tt>simple</tt> forms, the <tt>PATH</tt> parameter can point to a file or directory. The <tt>simple</tt>
155form will place the resource in the bundle JAR with only the file name,
156i.e., without any path component. For example, including <tt>src/main/resources/a/b.c</tt> will result in a resource <tt>b.c</tt> in the root of the bundle JAR. If the <tt>PATH</tt>
157points to a directory, the entire directory hierarchy is copied into
158the resulting bundle JAR file relative to the specified directory. If a
159specific resource must be placed into a subdirectory of the bundle jar,
160then use the <tt>assignment</tt> form, where the first path is the the
161destination path (including file name if the resource is a file) and
162the second path is the resource to copy. The <tt>inline</tt> form requires a ZIP or JAR file, which will be completely expanded in the bundle JAR.</p>
163
164<p>If a resource clause is specified inside of "{ ... }" brackets, then
165variable substitution will be performed on the resource, where
166variables in the resources are denoted with "${ ... }" syntax.</p>
167
168<h3><a name="MavenBundlePlugin(BND)-{{&lt;ImportPackage&gt;}}"></a><tt>&lt;Import-Package&gt;</tt></h3>
169
170<p>The <tt>&lt;Import-Package&gt;</tt> instruction is a list of
171packages that are required by the bundle's contained packages. The
172default for this header is "*", resulting in importing all referred
173packages. This header rarely has to be explicitly specified. However,
174in certain cases when there is an unwanted import, such an import can
175be removed by using a negation package pattern. The package patterns
176work in the same way as for <tt>&lt;Export-Package&gt;</tt>, which means they are ordered. For example, if you wanted to import all packages except <tt>org.foo.impl</tt> you would specify "<tt>!org.foo.impl,*</tt>"</p>
177
178<p><a name="MavenBundlePlugin(BND)-defaultbehavior"></a></p>
179
180<h2><a name="MavenBundlePlugin(BND)-DefaultBehavior"></a>Default Behavior</h2>
181
182<p>To use this plugin, very little information is required by BND. As
183part of the Maven integration, the plugin tries to set reasonable
184defaults for various instructions. For example:</p>
185<ul>
186 <li><tt>&lt;Bundle-SymbolicName&gt;</tt> is assumed to be "<tt>${groupId}.${artifactId</tt>}".</li>
187 <li><tt>&lt;Export-Package&gt;</tt> is assumed to be "<tt>${groupId}.${artifactId}.*</tt>", unless <tt>&lt;Private-Package&gt;</tt> is specified, then <tt>&lt;Export-Package&gt;</tt> is assumed to be empty.</li>
188 <li><tt>&lt;Private-Package&gt;</tt> is assumed to be empty by default.</li>
189 <li><tt>&lt;Import-Package&gt;</tt> is assumed to be "<tt>*</tt>", which imports everything referred to by the bundle content, but not contained in the bundle.</li>
190 <li><tt>&lt;Include-Resource&gt;</tt> is assumed to be "<tt>src/main/resources/</tt>",
191which will copy the specified project directory hierarchy into the
192resulting bundle JAR file, mirroring standard Maven behavior.</li>
193 <li><tt>&lt;Bundle-Version&gt;</tt> is assumed to be "<tt>${pom.version</tt>}" with '-' character separator of the qualifier replaced with a '.' character.</li>
194 <li><tt>&lt;Bundle-Name&gt;</tt> is assumed to be "<tt>${pom.name</tt>}".</li>
195 <li><tt>&lt;Bundle-Description&gt;</tt> is assumed to be "<tt>${pom.description</tt>}".</li>
196 <li><tt>&lt;Bundle-License&gt;</tt> is assumed to be "<tt>${pom.licenses</tt>}".</li>
197 <li><tt>&lt;Bundle-Vendor&gt;</tt> is assumed to be "<tt>${pom.organization.name</tt>}".</li>
198 <li><tt>&lt;Bundle-DocURL&gt;</tt> is assumed to be "<tt>${pom.organization.url</tt>}".</li>
199</ul>
200
201
202<p>Since the plugin creates bundles for OSGi R4, it hard codes <tt>Bundle-ManifestVersion</tt>
203to be '2'. Additionally, it generates imports for every export to
204ensure package substitutability, which is very important when working
205with collaborating services. It is possible to override any of these
206values (except <tt>Bundle-ManifestVersion</tt>) just by specifying the desired value in the plugin configuration section of the POM file.</p>
207
208<p><a name="MavenBundlePlugin(BND)-howto"></a></p>
209
210<h1><a name="MavenBundlePlugin(BND)-Detailed&quot;HowTo&quot;"></a>Detailed "How To"</h1>
211
212<h2><a name="MavenBundlePlugin(BND)-GetMaven2"></a>Get Maven2</h2>
213
214<p>The first step in the process of using the plugin is downloading and
215installing the latest version of the Maven2 runtime. The latest Maven2
216release and instuctions for getting started with Maven2 can be found at
217the <span class="nobr"><a href="http://maven.apache.org/index.html" title="Visit page outside Confluence" rel="nofollow">Maven website<sup><img class="rendericon" src="maven-bundle-plugin-bnd_files/linkext7.gif" alt="" align="absmiddle" border="0" height="7" width="7"></sup></a></span>.</p>
218
219<h2><a name="MavenBundlePlugin(BND)-UsingthePlugin"></a>Using the Plugin</h2>
220
221<p>To use the maven-bundle-plugin, you first need to add the plugin and
222some appropriate plugin configuration to your bundle project's POM.
223Below is an example of a simple OSGi bundle POM for Maven2:</p>
224<div class="preformatted"><div class="preformattedContent">
225<pre>&lt;project&gt;
226 &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
227 &lt;groupId&gt;my-osgi-bundles&lt;/groupId&gt;
228 &lt;artifactId&gt;examplebundle&lt;/artifactId&gt;
229 &lt;packaging&gt;bundle&lt;/packaging&gt; &lt;!-- (1) --&gt;
230 &lt;version&gt;1.0&lt;/version&gt;
231 &lt;name&gt;Example Bundle&lt;/name&gt;
232 &lt;dependencies&gt;
233 &lt;dependency&gt;
234 &lt;groupId&gt;org.apache.felix&lt;/groupId&gt;
235 &lt;artifactId&gt;org.osgi.core&lt;/artifactId&gt;
236 &lt;version&gt;0.8.0-incubator&lt;/version&gt;
237 &lt;/dependency&gt;
238 &lt;/dependencies&gt;
239 &lt;build&gt;
240 &lt;plugins&gt;
241 &lt;plugin&gt; &lt;!-- (2) START --&gt;
242 &lt;groupId&gt;org.apache.felix&lt;/groupId&gt;
243 &lt;artifactId&gt;maven-bundle-plugin&lt;/artifactId&gt;
244 &lt;extensions&gt;true&lt;/extensions&gt;
245 &lt;configuration&gt;
246 &lt;instructions&gt;
247 &lt;Export-Package&gt;com.my.company.api&lt;/Export-Package&gt;
248 &lt;Private-Package&gt;com.my.company.*&lt;/Private-Package&gt;
249 &lt;Bundle-Activator&gt;com.my.company.Activator&lt;/Bundle-Activator&gt;
250 &lt;/instructions&gt;
251 &lt;/configuration&gt;
252 &lt;/plugin&gt; &lt;!-- (2) END --&gt;
253 &lt;/plugins&gt;
254 &lt;/build&gt;
255 &lt;repositories&gt;
256 &lt;repository&gt; &lt;!-- (3) START --&gt;
257 &lt;id&gt;apache.m2.incubator&lt;/id&gt;
258 &lt;name&gt;Apache M2 Incubator Repository&lt;/name&gt;
259 &lt;url&gt;http://people.apache.org/repo/m2-incubating-repository/&lt;/url&gt;
260 &lt;/repository&gt; &lt;!-- (3) END --&gt;
261 &lt;/repositories&gt;
262 &lt;pluginRepositories&gt;
263 &lt;pluginRepository&gt; &lt;!-- (4) START --&gt;
264 &lt;id&gt;apache.m2.incubator&lt;/id&gt;
265 &lt;name&gt;Apache M2 Incubator Repository&lt;/name&gt;
266 &lt;url&gt;http://people.apache.org/repo/m2-incubating-repository/&lt;/url&gt;
267 &lt;/pluginRepository&gt; &lt;!-- (4) END --&gt;
268 &lt;/pluginRepositories&gt;
269&lt;/project&gt;
270</pre>
271</div></div>
272<p>There are four main things to note: (1) the <tt>&lt;packaging&gt;</tt>
273specifier must be "bundle", (2) the plugin and configuration must be
274specified (the configuration section is where you will issue
275instructions to the plugin), and the snapshot repository to resolve
276dependencies (3) and plugins (4).</p>
277
278<h2><a name="MavenBundlePlugin(BND)-RealWorldExample"></a>Real-World Example</h2>
279
280<p>Consider this more real-world example using Felix' Log Service
281implementation. The Log Service project is comprised of a single
282package: <tt>org.apache.felix.log.impl</tt>. It has a dependency on
283the core OSGi interfaces as well as a dependency on the compendium OSGi
284interfaces for the specific log service interfaces. The following is
285its POM file:</p>
286<div class="preformatted"><div class="preformattedContent">
287<pre>&lt;project&gt;
288 &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
289 &lt;groupId&gt;org.apache.felix&lt;/groupId&gt;
290 &lt;artifactId&gt;org.apache.felix.log&lt;/artifactId&gt;
291 &lt;packaging&gt;bundle&lt;/packaging&gt;
292 &lt;name&gt;Apache Felix Log Service&lt;/name&gt;
293 &lt;version&gt;0.8.0-SNAPSHOT&lt;/version&gt;
294 &lt;description&gt;
295 This bundle provides an implementation of the OSGi R4 Log service.
296 &lt;/description&gt;
297 &lt;dependencies&gt;
298 &lt;dependency&gt;
299 &lt;groupId&gt;${pom.groupId}&lt;/groupId&gt;
300 &lt;artifactId&gt;org.osgi.core&lt;/artifactId&gt;
301 &lt;version&gt;0.8.0-incubator&lt;/version&gt;
302 &lt;/dependency&gt;
303 &lt;dependency&gt;
304 &lt;groupId&gt;${pom.groupId}&lt;/groupId&gt;
305 &lt;artifactId&gt;org.osgi.compendium&lt;/artifactId&gt;
306 &lt;version&gt;0.9.0-incubator-SNAPSHOT&lt;/version&gt;
307 &lt;/dependency&gt;
308 &lt;/dependencies&gt;
309 &lt;build&gt;
310 &lt;plugins&gt;
311 &lt;plugin&gt;
312 &lt;groupId&gt;org.apache.felix&lt;/groupId&gt;
313 &lt;artifactId&gt;maven-bundle-plugin&lt;/artifactId&gt;
314 &lt;extensions&gt;true&lt;/extensions&gt;
315 &lt;configuration&gt;
316 &lt;instructions&gt;
317 &lt;Export-Package&gt;org.osgi.service.log&lt;/Export-Package&gt;
318 &lt;Private-Package&gt;org.apache.felix.log.impl&lt;/Private-Package&gt;
319 &lt;Bundle-SymbolicName&gt;${pom.artifactId}&lt;/Bundle-SymbolicName&gt;
320 &lt;Bundle-Activator&gt;${pom.artifactId}.impl.Activator&lt;/Bundle-Activator&gt;
321 &lt;Export-Service&gt;org.osgi.service.log.LogService,org.osgi.service.log.LogReaderService&lt;/Export-Service&gt;
322 &lt;/instructions&gt;
323 &lt;/configuration&gt;
324 &lt;/plugin&gt;
325 &lt;/plugins&gt;
326 &lt;/build&gt;
327 &lt;repositories&gt;
328 &lt;repository&gt;
329 &lt;id&gt;apache.m2.incubator&lt;/id&gt;
330 &lt;name&gt;Apache M2 Incubator Repository&lt;/name&gt;
331 &lt;url&gt;http://people.apache.org/repo/m2-incubating-repository/&lt;/url&gt;
332 &lt;/repository&gt;
333 &lt;/repositories&gt;
334 &lt;pluginRepositories&gt;
335 &lt;pluginRepository&gt;
336 &lt;id&gt;apache.m2.incubator&lt;/id&gt;
337 &lt;name&gt;Apache M2 Incubator Repository&lt;/name&gt;
338 &lt;url&gt;http://people.apache.org/repo/m2-incubating-repository/&lt;/url&gt;
339 &lt;/pluginRepository&gt;
340 &lt;/pluginRepositories&gt;
341&lt;/project&gt;
342</pre>
343</div></div>
344<p>Notice that the <tt>&lt;Export-Package&gt;</tt> instruction
345specifies that the bundle exports the Log Service package, even though
346this package is not contained in the bundle project. By declaring this,
347the plugin will copy the Log Service package into the resulting bundle
348JAR file. This is useful in this case because now the bundle can
349resolve without having to download the entire compendium bundle. The
350resulting manifest for the Log Service bundle looks like this (notice
351how the imports/exports automatically have version information
352associated with them, which was obtained from packageinfo files in the
353source packages):</p>
354<div class="preformatted"><div class="preformattedContent">
355<pre>Manifest-Version: 1
356Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt
357Bundle-Activator: org.apache.felix.log.impl.Activator
358Import-Package: org.osgi.framework;version=1.3, org.osgi.service.log;v
359 ersion=1.3
360Include-Resource: src/main/resources
361Export-Package: org.osgi.service.log;uses:=org.osgi.framework;version=
362 1.3
363Bundle-Version: 0.8.0.SNAPSHOT
364Bundle-Name: Apache Felix Log Service
365Bundle-Description: This bundle provides an implementation of the OSGi
366 R4 Log service.
367Private-Package: org.apache.felix.log.impl
368Bundle-ManifestVersion: 2
369Export-Service: org.osgi.service.log.LogService,org.osgi.service.log.L
370 ogReaderService
371Bundle-SymbolicName: org.apache.felix.log
372</pre>
373</div></div>
374<p>The resulting bundle JAR file has the following content (notice how
375the LICENSE and NOTICE files were automatically copied from the <tt>src/main/resources/</tt> directory of the project):</p>
376<div class="preformatted"><div class="preformattedContent">
377<pre>META-INF/MANIFEST.MF
378LICENSE
379META-INF/
380META-INF/maven/
381META-INF/maven/org.apache.felix/
382META-INF/maven/org.apache.felix/org.apache.felix.log/
383META-INF/maven/org.apache.felix/org.apache.felix.log/pom.properties
384META-INF/maven/org.apache.felix/org.apache.felix.log/pom.xml
385NOTICE
386org/
387org/apache/
388org/apache/felix/
389org/apache/felix/log/
390org/apache/felix/log/impl/
391org/apache/felix/log/impl/Activator.class
392org/apache/felix/log/impl/Log.class
393org/apache/felix/log/impl/LogEntryImpl.class
394org/apache/felix/log/impl/LogException.class
395org/apache/felix/log/impl/LogListenerThread.class
396org/apache/felix/log/impl/LogNode.class
397org/apache/felix/log/impl/LogNodeEnumeration.class
398org/apache/felix/log/impl/LogReaderServiceFactory.class
399org/apache/felix/log/impl/LogReaderServiceImpl.class
400org/apache/felix/log/impl/LogServiceFactory.class
401org/apache/felix/log/impl/LogServiceImpl.class
402org/osgi/
403org/osgi/service/
404org/osgi/service/log/
405org/osgi/service/log/LogEntry.class
406org/osgi/service/log/LogListener.class
407org/osgi/service/log/LogReaderService.class
408org/osgi/service/log/LogService.class
409org/osgi/service/log/package.html
410org/osgi/service/log/packageinfo
411</pre>
412</div></div>
413
414<h2><a name="MavenBundlePlugin(BND)-BuildingthePlugin"></a>Building the Plugin</h2>
415
416<p>The plugin is hosted at the Apache Felix incubator project. The
417following steps describe how to build and install the plugin into your
418local Maven2 repository.</p>
419
420<p>Using the SVN client of your choice, checkout the maven-bundle-plugin project.</p>
421<div class="preformatted"><div class="preformattedContent">
422<pre>$ svn co http://svn.apache.org/repos/asf/felix/trunk/tools/maven2/maven-bundle-plugin
423</pre>
424</div></div>
425<p>Using Maven2, build and install the maven-bundle-plugin by issuing
426the following Maven2 command in the project directory that was created
427as a result of the previous step.</p>
428<div class="preformatted"><div class="preformattedContent">
429<pre>$ mvn install
430</pre>
431</div></div>
432 </div>
433
434</body></html>