| <html><head><META http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Application Versioning</title><meta content="DocBook XSL Stylesheets V1.76.0" name="generator"><link rel="home" href="index.html" title="Virgo Programmer Guide"><link rel="up" href="ch04.html" title="Chapter 4. Developing Applications"><link rel="prev" href="ch04s09.html" title="Application Trace"><link rel="next" href="ch05.html" title="Chapter 5. Migrating to OSGi"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table summary="Navigation header" width="100%"><tr><td align="left" width="20%"><a accesskey="p" href="ch04s09.html">Prev</a> </td><th align="center" width="60%"> </th><td align="right" width="20%"> <a accesskey="n" href="ch05.html">Next</a></td></tr></table><hr></div><div class="section" title="Application Versioning"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="developing-applications-versioning"></a>Application Versioning</h2></div></div></div><p> | |
| In much the same way that individual OSGi bundles can be versioned, Virgo allows applications to be versioned. How exactly you do this depends on how you have packaged the application: | |
| </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">If you package your application using a PAR, you version the application by using the <code class="literal">Application-Version</code> header in the <code class="code">MANIFEST.MF</code> file of the PAR file.</li><li class="listitem">If you use a plan to describe the artifacts that make up your application, you version it by using the <code class="code">version</code> attribute of the <code class="code"><plan></code> root element of the plan’s XML file.</li><li class="listitem">If your application consists of a single bundle, you version it in the standard OSGi way: by using the <code class="literal">Bundle-Version</code> header of the <code class="code">MANIFEST.MF</code> file of the bundle.</li></ul></div><p> | |
| </p><p>Virgo uses an application’s version to prevent clashes when multiple versions of the same application are deployed at | |
| the same time. For example, the application trace support described in <a class="xref" href="ch04s09.html" title="Application Trace">Application Trace</a>, | |
| includes the application’s name and version in the file path. This ensures that each version of the same application has its | |
| own trace or logging file. | |
| </p></div><div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%"><a accesskey="p" href="ch04s09.html">Prev</a> </td><td align="center" width="20%"><a accesskey="u" href="ch04.html">Up</a></td><td align="right" width="40%"> <a accesskey="n" href="ch05.html">Next</a></td></tr><tr><td valign="top" align="left" width="40%"> </td><td align="center" width="20%"><a accesskey="h" href="index.html">Home</a></td><td valign="top" align="right" width="40%"> </td></tr></table></div></body></html> |