No Format

To: announce@apache.org, user@sqoop.apache.org, dev@sqoop.apache.org
Subject: [ANNOUNCE] Apache Sqoop 1.99.1 released

The Apache Sqoop team is pleased to announce the release of Sqoop 1.99.1.

This is the first cut of Sqoop2 branch. Major step forward of the project.

Apache Sqoop is a tool designed for efficiently transferring bulk data between Apache Hadoop and structured datastores, such as relational databases.

The release is available here:
http://www.apache.org/dyn/closer.cgi/sqoop/1.99.1

The full change log is available here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311320&version=12323641

Your help and feedback is more than welcome. For more information on how to report problems
and to get involved, visit the project website at http://sqoop.apache.org/.

The Apache Sqoop Team

_JARCEC_END_

Publish binary artifacts in Maven Repository

Note

title	These instructions will change when Sqoop moves to maven builds

Currently Sqoop is built using ant and thus the process necessary for publishing its binary artifacts in Maven repository is manual. Once Sqoop migrates to using Maven build (which is the default in Sqoop 2), these steps will need to be updated accordingly.

Sqoop already has a Nexus repository setup, thanks to INFRA-4310. The following steps outline how you can publish Sqoop binaries to this repository.

Setup Maven settings

Follow the details provided in Maven Password Encryption Guide to set up a master password for your system.

Once the master password has been created, update your maven settings file (~/.m2/settings.xml) to have the following server entries:

Code Block


<settings>
  ...
  <servers>
    <server>
      <id>apache.snapshots.https</id>
      <username>your-asf-user-name</username>
      <password>your-encrypted-asf-password</password>
    </server>
    <server>
      <id>apache.releases.https</id>
      <username>your-asf-user-name</username>
      <password>your-encrypted-asf-password</password>
    </server>
    <server>
      <id>apache.staging.https</id>
      <username>your-asf-user-name</username>
      <password>your-encrypted-asf-password</password>
    </server>
  </servers>
  ...
</settings>

Prepare artifacts to publish

In a newly created directory, checkout the sources from the appropriate release tag location. For example, for the release 1.4.0-incubating the sources will need to be checked out from https://svn.apache.org/repos/asf/incubator/sqoop/tags/release-1.4.0-rc1/. Once you have the sources, build them to generate the binaries. For example:

Code Block
$ svn co https://svn.apache.org/repos/asf/incubator/sqoop/tags/release-1.4.0-rc1/ ... $ cd release-1.4.0-rc1 $ ant jar-all ... BUILD SUCCESSFUL Total time: 11 seconds $

Install to local maven cache

Before you do this step, remove any previously installed Sqoop artifacts from your local maven cache. You can do this by running the following command:

Code Block
$ rm -rf ~/.m2/repository/com/cloudera/sqoop ~/.m2/repository/org/apache/sqoop

Now run the following command to install the newly checked-out and built artifacts of Sqoop from the previous step to your local maven cache.

Code Block
$ ant mvn-install ... BUILD SUCCESSFUL Total time: 6 seconds $

This will result in copying of the built artifacts and generated POM file into your local maven cache.

Deploy main artifact to staging repo

Once the artifacts are in your local cache, you can now deploy them to Nexus staging repository.

Start out by going into the directory where the main artifact is generated. Once there, make sure that the generated POM file looks accurate and if not, fix it manually. Then run the following commands to deploy the main artifact.

Code Block


$ cd ~/.m2/repository/org/apache/sqoop/sqoop/1.4.0-incubating

$ ls -l
total 1108
-rw-r--r-- 1 arvind staff 532981 Jan 11 16:32 sqoop-1.4.0-incubating-sources.jar
-rw-r--r-- 1 arvind staff 590086 Jan 11 16:32 sqoop-1.4.0-incubating.jar
-rw-r--r-- 1 arvind staff   1670 Jan 11 16:32 sqoop-1.4.0-incubating.pom
$ mvn gpg:sign-and-deploy-file -Dfile=./sqoop-1.4.0-incubating.jar -DrepositoryId=apache.staging.https -Durl=https://repository.apache.org/service/local/staging/deploy/maven2/ -DpomFile=./sqoop-1.4.0-incubating.pom -Dgpg.keyname=<your-gpg-keyname>
...
[INFO] Metadata[project org.apache.sqoop:sqoop].filename = sqoop-1.4.0-incubating.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 9.169s
[INFO] Finished at: Wed Jan 11 16:58:35 PST 2012
[INFO] Final Memory: 6M/81M
[INFO] ------------------------------------------------------------------------

This will result in the signing and deployment of the main artifact sqoop-1.4.0-incubating.jar in this case, to the staging repository. If all goes well you should be able to point your browser to Apache Nexus Repository and clicking on the Staging Repository link on the left navigation column. When you select the staging repository in the right pane, the pane will split into a content pane below that shows how the content of the staging repository created by the above command. The following screenshot illustrates what this looks like.

Image Removed

Deploy test artifact to staging repo

To deploy the test artifact to the staging repo, you must copy the generated test artifact to the same directory as that of the main directory so that you can use the main artifact POM and specify a classifier. Here are the commands to do that:

Code Block


$ ls -l
total 1116
-rw-r--r-- 1 arvind staff 532981 Jan 11 16:32 sqoop-1.4.0-incubating-sources.jar
-rw-r--r-- 1 arvind staff 590086 Jan 11 16:32 sqoop-1.4.0-incubating.jar
-rw-r--r-- 1 arvind staff    833 Jan 11 16:58 sqoop-1.4.0-incubating.jar.asc
-rw-r--r-- 1 arvind staff   1668 Jan 11 16:58 sqoop-1.4.0-incubating.pom
-rw-r--r-- 1 arvind staff    833 Jan 11 16:58 sqoop-1.4.0-incubating.pom.asc

$ cp ../../sqoop-test/1.4.0-incubating/sqoop-test-1.4.0-incubating.jar .

$ ls -l
total 1392
-rw-r--r-- 1 arvind staff 532981 Jan 11 16:32 sqoop-1.4.0-incubating-sources.jar
-rw-r--r-- 1 arvind staff 590086 Jan 11 16:32 sqoop-1.4.0-incubating.jar
-rw-r--r-- 1 arvind staff    833 Jan 11 16:58 sqoop-1.4.0-incubating.jar.asc
-rw-r--r-- 1 arvind staff   1668 Jan 11 16:58 sqoop-1.4.0-incubating.pom
-rw-r--r-- 1 arvind staff    833 Jan 11 16:58 sqoop-1.4.0-incubating.pom.asc
-rw-r--r-- 1 arvind staff 278892 Jan 11 17:06 sqoop-test-1.4.0-incubating.jar

$ mvn gpg:sign-and-deploy-file -Dfile=./sqoop-test-1.4.0-incubating.jar -DrepositoryId=apache.staging.https -Durl=https://repository.apache.org/service/local/staging/deploy/maven2/ -DpomFile=./sqoop-1.4.0-incubating.pom -Dgpg.keyname=<your-gpg-keyname> -Dclassifier=tests
...
[INFO] Metadata[project org.apache.sqoop:sqoop].filename = sqoop-1.4.0-incubating.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11.160s
[INFO] Finished at: Wed Jan 11 17:10:01 PST 2012
[INFO] Final Memory: 6M/81M
[INFO] ------------------------------------------------------------------------
$

If this command succeeds, you can now see the test artifacts deployed in the staging repository as well. Go the the browser and click on the refresh button on the content area to reload the contents of the staging repository. The following screen shot is an example of how the staging repository may look like after these steps.

Image Removed

Close and Release staging repository

In the Nexus main content pane, make sure the staging repository you are working with is selected with a check mark, and click the "Close" button on top. This causes Nexus to verify the signatures and if everything is valid, it will result in successful closing of the repository. If there are any failures due to invalid signatures, you will have to drop the repository and redo the steps outlined in this section again.

Once the repository is closed, you can promote it to release status by clicking on the "Release" button on top. This allows the artifacts in this staging repository to be published to release repository immediately. Once the release has propagated, you should receive a confirmation email from Nexus stating that the artifacts are now available in the release repository.

Updating the website and the wiki with the new Sqoop bits:

1. Configure your Apache credentials in your maven settings.xml file (usually in ~/.m2/settings.xml)

Code Block
<servers> <server> <id>apache.releases.https</id> <username>APACHE-ID</username> <password>APACHE-PASSWORD</password> </server> </servers>

2. Go to release branch (tag that was released)

3. Create, sign and deploy artifacts into staging repository

Code Block
for version in 100 200; do mvn clean deploy -Psign -Dhadoop.profile=$version ; done

4. Login to https://repository.apache.org^{Image Added} and select "Staging Repositories" under "Build Promotion" menu on the left.

5. Select org.apache.sqoop from the list of repositories and click "Close" using "Apache Sqoop 1.99.1" as description.

6. Select org.apache.sqoop from the list of repositories and click "Release" using "Apache Sqoop 1.99.1 artifacts" as descriptionhttps://cwiki.apache.org/confluence/display/SQOOP/How+to+Update+Project+Website

Child pages

Versions Compared

Old Version 10

New Version 11

Key

_JARCEC_END_

Publish binary artifacts in Maven Repository

Setup Maven settings

Prepare artifacts to publish

Install to local maven cache

Deploy main artifact to staging repo

Deploy test artifact to staging repo

Close and Release staging repository

Updating the website and the wiki with the new Sqoop bits:

Child pages

Page History

Versions Compared

Old Version 10

New Version 11

Key

_JARCEC_END_

Publish binary artifacts in Maven Repository

Setup Maven settings

Prepare artifacts to publish

Install to local maven cache

Deploy main artifact to staging repo

Deploy test artifact to staging repo

Close and Release staging repository

Updating the website and the wiki with the new Sqoop bits: