geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache Geronimo Project Management > Geronimo 2.2 release tips
Date Tue, 30 Nov 2010 06:50:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/1810/9/1/_/styles/combined.css?spaceKey=GMOxPMGT&amp;forWysiwyg=true"
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="">Geronimo
2.2 release tips</a></h2>
    <h4>Page <b>edited</b> by             <a href="">Rex
                         <h4>Changes (1)</h4>
<div id="page-diffs">
            <table class="diff" cellpadding="0" cellspacing="0">
            <tr><td class="diff-added-lines" style="background-color: #dfd;">h1.
Special instructions for releasing the Server (used on Geronimo 2.2) <br>-by David Jencks
            <tr><td class="diff-unchanged" > <br>h2. New Nexus Release Guidelines
            <tr><td class="diff-snipped" >...<br></td></tr>
</div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <h1><a name="Geronimo2.2releasetips-SpecialinstructionsforreleasingtheServer%28usedonGeronimo2.2%29"></a>Special
instructions for releasing the Server (used on Geronimo 2.2)</h1>
<p>-by David Jencks</p>

<h2><a name="Geronimo2.2releasetips-NewNexusReleaseGuidelines"></a>New Nexus
Release Guidelines</h2>

<p>Follow the new <a href=""
class="external-link" rel="nofollow">Apache Release process for Nexus</a>, which
all projects must use moving forward.  These steps apply to a given project if:</p>
	<li>It uses Genesis 2.x as a parent POM</li>
	<li>It uses the following for the Snapshot and Release repos in distributionManagement
		<li><a href="" class="external-link" rel="nofollow"></a></li>

<p>For additional details on the Nexus repo changes, take a look at the doc links in
the following JIRA, until we have a new process documented -<br/>
<a href="" class="external-link" rel="nofollow">INFRA-1896</a></p>

<h3><a name="Geronimo2.2releasetips-SpecialinstructionsforreleasingtheServer%28usedonGeronimo2.2%29"></a>Special
instructions for releasing the Server (used on Geronimo 2.2)</h3>

<h4><a name="Geronimo2.2releasetips-Overview"></a>Overview</h4>

<p>Run the normal release plugin steps, but with the following additional profiles:</p>
<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
<pre>mvn release:prepare -Pall-subprojects -Papache-release -Dtest=false
mvn release:perform -Pall-subprojects -Papache-release -Dtest=false

<h4><a name="Geronimo2.2releasetips-Preparationanddiscussion"></a>Preparation
and discussion</h4>

<p>We have a lot of server bits that don't normally get run in a build and shouldn't
be released.  These are typically integration tests or test servers for plugins.  All these
projects have to be built during the release so the versions get updated properly.  Since
mistakes here won't cause build problems except during releases, you have to check carefully
that all projects are built in the all-subprojects profile.  Note that integration tests are
often run from non-pom packaging projects so you have to add such projects as modules to the
closest parent project that is pom packaging.</p>

<p>When I tried it the versions plugin did not successfully update all the child projects
in testsuite, I had to actually run the release process to determine if all modules were getting
their versions updated.</p>

<p>Many projects such as integration tests, test servers, and the testsuite should not
get deployed.  You can arrange this by including this configuration in the topmost pom that
should not be deployed:</p>


<p>in build/plugins.</p>
        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;">
            <a href=""
class="grey">Change Notification Preferences</a>
        <a href="">View
        <a href="">View
        <a href=";showCommentArea=true#addcomment">Add

View raw message