Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Tue, 12 Oct 2010 17:25:25 -0000
Message-ID: <20101012172525.40387.39861@eosnew.apache.org>
Subject: 
 =?utf-8?q?=5BDb-derby_Wiki=5D_Update_of_=22DerbySnapshotOrRelease=22_by_R?=
 =?utf-8?q?ichardHillegas?=

Dear Wiki user,

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

The "DerbySnapshotOrRelease" page has been changed by RichardHillegas.
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease?action=3Ddiff&rev1=
=3D159&rev2=3D160

--------------------------------------------------

  =

  =3D Deprecated instructions =3D
  =

+ See DeprecatedReleaseInstructions
  =

-  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, a=
nd put the bin directory into your path so that you can run maven commands.
- =

-    {i} As of this writing, the latest 1.x version of Maven was 1.1.
- =

-   a. `cd` into Derby's `maven` directory. Typically this will be in the s=
ame sandbox that you used to build the release, but this is not strictly re=
quired.
- =

-   a. Edit `project.xml` so that it contains the correct version number fo=
r this release between the <currentversion> tags. =

- =

-   a. Edit `project.properties`:
-    * Add username, and password for your account on `people.apache.org` s=
o 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 j=
ars. `jars/insane` is the default, so if you backed up the jars somewhere e=
lse when you built the release you must adjust this property accordingly. Y=
ou 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=3Dapache`. It commented out by default t=
o prevent accidental deployments. =

- =

-    Your local diff should look something like:
- =

-    {{{
- sanity=3Dinsane
- -derby.jars=3D../../jars/${sanity}
- +derby.jars=3D/path/to/maven/jars
-  =

- -#maven.repo.list=3Dapache
- +maven.repo.list=3Dapache
-  maven.repo.apache=3Dscpexe://people.apache.org
-  maven.repo.apache.directory=3D/www/people.apache.org/repo/m1-ibiblio-rsy=
nc-repository
- -maven.repo.apache.username=3D
- -maven.repo.apache.password=3D
- +maven.repo.apache.username=3Dyou
- +maven.repo.apache.password=3Dsecret
-  maven.repo.apache.group=3Ddb}}}
- =

-   a. Run the Maven commands. =

-    * 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.
- =

-    * Run `maven clean` to attain the `multiproject:clean` goal to clean u=
p the maven tree.
-    * Run `maven multiproject:deploy` to copy all the artifacts into the a=
pachecvs repository.
- =

-    <!> The `multiproject:deploy` command will not work unelss you uncomme=
nt the `maven.repo.list` property in `project.properties`.
- =

-    {i} This does not build using maven, it works by copying the jars poin=
ted to by `${derby.jars}` (`jars/${sanity}` by default).
- =

-   a. Sign the individual jars. =

-    Unfortunately, Maven renames the jars during deployment, so the jars n=
ow found in the Maven repository have the version number embedded in the fi=
le name. E.g `derby.jar` has become `derby-x.y.z.w.jar`. The name of the si=
gnature file needs to same as the name of jar with the `asc` extension, but=
 Maven apparently knows nothing about signatures, so we have to create corr=
ectly named signatures by hand. The following script signs and renames the =
jars appropriately, and should be run in the `${derby.jars}` directory. =

- =

-    {{{
- for i in *.jar
- do
-   gpg --armor --detach-sign $i   // enter your PGP passphrase for each it=
eration.
- done
- for i in *.jar.asc
- do
-   PREFIX=3D`echo $i | sed 's/.jar.asc//g'`
-   NEWNAME=3D$PREFIX-x.y.z.w.jar.asc   //use the correct version number fo=
r this release.
-   mv $i $NEWNAME
- done}}}
- =

-   a. Upload the signatures to the jars directory:
-    {{{
- sftp {username}@people.apache.org
- cd /www/people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.der=
by/jars/
- put *.jar.asc}}}
- =

-    {i} If you don't upload the signatures for the jar files, you will pro=
bably receive an email saying that you did not upload appropriate PGP signa=
tures for the new files added to `www.apache.org/dist/`.
- =

-   a. {X} Ensure that the uploaded files have useful permissions. They nee=
d to be rw-r--r-- (chmod 644).
- =

-   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 dep=
loyed to that repository as well. See [[http://issues.apache.org/jira/brows=
e/DERBY-1378|DERBY-1378]] for more information on the automatic conversion =
to Maven 2.
- =

-  1. {X} The maven deploy step expects to do scp without prompting for pas=
swords. If you can normally do scp, but get an error reflecting 'Failed to =
deploy', in org.apache.maven.wagon.providers.ssh.external.!ScpExternalWagon=
.put, you may not have this set up. If this is the problem, one workaround =
is to do the copying manually, as outlined in the next section. Or you can =
do the following steps (and ensure that you append .ssh/authorized_keys, no=
t overwrite):
-    {{{
- $ ssh-keygen -t dsa
- --> press ENTER when prompted for a pass-phrase to get a null phrase.
- $ scp ~/.ssh/id_dsa.pub you@people.apache.org:
- >Password:...
- $ ssh you@people.apache.org
- >Password:...
- $ cat id_dsa.pub >> .ssh/authorized_keys}}}
- =

-  1. {X} Maven may not work for you especially on Windows. If Maven does n=
ot copy the build artifacts to subdirectories under `/www/people.apache.org=
/repo/m1-ibiblio-rsync-repository/org.apache.derby/`, then you will have to=
 do this yourself. In this scenario, you must use Maven to deploy the build=
 artifacts to your local file system, sign them and then sftp the results t=
o people.apache.org. =

-   a. To deploy the build artifacts to your local file system, set up proj=
ect.properties something like this:
- =

-    {{{
- maven.repo.list=3Dapache
- maven.repo.apache=3Dfile:///home/myself/zdir
- maven.repo.apache.directory=3Dgarbage
- maven.repo.apache.username=3Dgarbage
- maven.repo.apache.password=3Dgarbage
- maven.repo.apache.group=3Dgarbage}}}
- =

-   a. Then do
- =

-    $ maven clean
- =

-    $ maven multiproject:deploy
- =

-    This will build the artifacts into a subtree rooted at /home/myself/zd=
ir/garbage. =

- =

-   a. Sign the jars using the following script:
-    {{{
-    for i in `ls *.jar`
-    do
-      gpg --armor --detach-sign $i
-    done
-    }}}
- =

-   a. Use sftp to bulk put the artifacts into the corresponding subdirecto=
ries of `www/people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.=
derby/`. Note that there are 3 directories of files (jars, poms, wars) whic=
h must be sftp'd from your machine to the tree on people.apache.org.
-=20