Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: derby-commits@db.apache.org
Date: Fri, 02 May 2008 12:05:21 -0000
Message-ID: <20080502120521.10054.90197@eos.apache.org>
Subject: [Db-derby Wiki] Update of "DerbySnapshotOrRelease" by DyreTjeldvoll

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by DyreTjeldvoll:
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease

------------------------------------------------------------------------------
   
  
   1. Deploy to Maven repository.
+   a. If you do not already have the latest Maven 1 distribution, [http://maven.apache.org/maven-1.x/start/download.html download it], unpack it, and put the bin directory into your path so that you can run maven commands.
  
-   {i} First, if you do not already have the latest Maven 1 distribution, download it from http://maven.apache.org/maven-1.x/start/download.html, unpack it, and put the bin directory into your path so that you can run maven commands. As of this writing, the latest 1.x version of Maven was 1.1.
+    {i} As of this writing, the latest 1.x version of Maven was 1.1.
  
+   a. `cd` into Derby's `maven` directory. {i} Typically this will be in the same sandbox that you used to build the release, but this is not strictly required.
+ 
-   a. Next, edit `project.xml` in the maven directory in the derby tree to contain the correct version number for this release between the <currentversion> tags. 
+   a. Edit `project.xml` so that it contains the correct version number for this release between the <currentversion> tags. 
  
-   a. Then, edit the `project.properties` to contain the correct protocol, username, and password for your account on `people.apache.org` so you can properly authenticate and copy the files to people. The scpexe protocol should work without problems, especially if you have an ssh public key already on people. `The project.properties` file in the maven directory should look something like this, for the maven.repo lines in the file:
+   a. Edit `project.properties`:
+    * Add username, and password for your account on `people.apache.org` so you can properly authenticate and copy the files to `people`. The scpexe protocol should work without problems, especially if you have an ssh public key already on `people`.
+    * Make sure `derby.jars` points to the directory holding the release jars. `jars/insane` is the default, so if you backed up the jars somewhere else when you built the release you must adjust this property accordingly. You also need modify this property if you are using a sandbox other than the one you used to build the release.
+    * Uncomment `#maven.repo.list=apache`. It commented out by default to prevent accidental deployments. 
  
+    Your local diff should look something like:
+ 
+    {{{sanity=insane
+ -derby.jars=../../jars/${sanity}
+ +derby.jars=/path/to/maven/jars
+  
+ -#maven.repo.list=apache
-    {{{maven.repo.list=apache
+ +maven.repo.list=apache
- maven.repo.apache=scpexe://people.apache.org
+  maven.repo.apache=scpexe://people.apache.org
- maven.repo.apache.directory=/www/www.apache.org/dist/java-repository
+  maven.repo.apache.directory=/www/people.apache.org/repo/m1-ibiblio-rsync-repository
+ -maven.repo.apache.username=
+ -maven.repo.apache.password=
- maven.repo.apache.username={your_username}
+ +maven.repo.apache.username=you
- maven.repo.apache.password={your_password}
+ +maven.repo.apache.password=secret
- maven.repo.apache.group=db}}}
+  maven.repo.apache.group=db}}}
  
+   a. Run the Maven commands. 
-   a. Then, cd into Derby's maven directory and
+    * cd into Derby's maven directory
+    * Run `maven` to attain the `multiproject:install` goal to install the artifacts into your local maven repo.
+    {X} Note: For 10.3.2.1 I had to type `maven multiproject:install` to get this to work.
- 
-    {{{$ maven   # will attain the multiproject:install goal to install the artifacts into your local maven repo. Note: For 10.3.2.1 I had to type maven multiproject:install to get this to work.
- 
-    $ maven clean   # will attain the multiproject:clean goal to clean up the maven tree
+    * Run `maven clean` to attain the `multiproject:clean` goal to clean up the maven tree.
+    * Run `maven multiproject:deploy` to copy all the artifacts into the apachecvs repository.
  
-    $ maven multiproject:deploy   # will copy all the artifacts into the apachecvs repository (note, for now this has been disabled by commenting out the maven.repo.list definition in project.properties).}}}
+    {X} The checked in version of `project.properties` disables this step by commenting out the `maven.repo.list` property.
+ 
+    {{{cd maven
+ maven
+ [...lots of output...]
+ maven clean
+ [...lots of output...]
+ maven multiproject:deploy
+ [...lots of output...]}}}
  
     {i} This does not build using maven, it works by copying the jars that ant built into jars/${sanity}.
  
@@ -614, +638 @@

     {{{sftp {username}@svn.apache.org
  cd /www/people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.derby/jars/
  put *.jar.asc}}}
+ 
+   a. Revert local modifications in the `maven` directory.
  
    {i} The deployment of the jars and poms to the Maven 1 repository will be automatically converted to appropriate jars and poms for Maven 2 and deployed to that repository as well. See [http://issues.apache.org/jira/browse/DERBY-1378 DERBY-1378] for more information on the automatic conversion to Maven 2.