ExternalVendorCode/corda
1
0
Fork 0
mirror of https://github.com/corda/corda.git synced 2025-06-01 15:10:54 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

edit rsync and tar info (#1214)

Browse Source 
* edit rsync and tar info

Edit rsync to copy repository into ~/.m2 so it overwrites the existing ~/.m2/repository rather than copy another repository sub-directory. Also, edit info on tar file to reflect that it's actually a tar.gz file and modify tar command to include -xvzf flags.

* Add word, compressed (@guyho)
This commit is contained in:
guyho 2018-07-12 03:59:01 -04:00 committed by Michele Sollecito
parent a23b3f4b29
commit 12759831fe
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/source/getting-set-up.rst
View File

@ -82,12 +82,12 @@ Download a sample project
1. Open a command prompt 1. Open a command prompt
2. Clone the CorDapp example repo by running ``git clone https://github.com/corda/cordapp-example`` 2. Clone the CorDapp example repo by running ``git clone https://github.com/corda/cordapp-example``
3. Move into the ``cordapp-example`` folder by running ``cd cordapp-example`` 3. Move into the ``cordapp-example`` folder by running ``cd cordapp-example``
4. Checkout the corresponding branch for Corda Enterprise 3.0 by running ``git checkout release-enterprise-V3`` in the current directory 4. Checkout the corresponding branch for Corda Enterprise 3.1 by running ``git checkout release-enterprise-V3`` in the current directory
Resolve Corda Enterprise binaries Resolve Corda Enterprise binaries
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The Corda Enterprise binaries are not available in a publicly accessible Maven repository. Instead, the Corda Enterprise The Corda Enterprise binaries are not available in a publicly accessible Maven repository. Instead, the Corda Enterprise
binaries will be made available to your organisation as a tarball (``corda-3.0-developer-pack.tar.gz``). binaries will be made available to your organisation as a compressed tarball (``corda-3.1-developer-pack.tar.gz``).
This tarball contains all of the Corda dependencies as they would appear in your local Maven repository located at This tarball contains all of the Corda dependencies as they would appear in your local Maven repository located at
``C:\Documents and Settings\{your-username}\.m2``. ``C:\Documents and Settings\{your-username}\.m2``.
@ -104,7 +104,7 @@ dependencies.
c. Add Corda Enterprise binaries to a local directory and register a local Maven repository pointing to this directory with Gradle. c. Add Corda Enterprise binaries to a local directory and register a local Maven repository pointing to this directory with Gradle.
.. note:: Upon receiving the binaries, the quickest way to get started developing your CorDapps is **option a**. This can .. note:: Upon receiving the binaries, the quickest way to get started developing your CorDapps is **option a**. This can
be done by firstly unpacking the ``corda-3.0-developer-pack.tar.gz`` tarball. Then, copy the unpacked be done by firstly unpacking the ``corda-3.1-developer-pack.tar.gz`` compressed tarball. Then, copy the unpacked
``respository`` folder to your local Maven repository located at ``C:\Documents and Settings\{your-username}\.m2``. ``respository`` folder to your local Maven repository located at ``C:\Documents and Settings\{your-username}\.m2``.
Run from the command prompt Run from the command prompt
@ -163,14 +163,14 @@ Download a sample project
1. Open a terminal 1. Open a terminal
2. Clone the CorDapp example repo by running ``git clone https://github.com/corda/cordapp-example`` 2. Clone the CorDapp example repo by running ``git clone https://github.com/corda/cordapp-example``
3. Move into the ``cordapp-example`` folder by running ``cd cordapp-example`` 3. Move into the ``cordapp-example`` folder by running ``cd cordapp-example``
4. Checkout the corresponding branch for Corda Enterprise 3.0 by running ``git checkout release-enterprise-V3`` in the current directory 4. Checkout the corresponding branch for Corda Enterprise 3.1 by running ``git checkout release-enterprise-V3`` in the current directory
.. _resolve-corda-enterprise-binaries: .. _resolve-corda-enterprise-binaries:
Resolve Corda Enterprise binaries Resolve Corda Enterprise binaries
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The Corda Enterprise binaries are not available in a publicly accessible Maven repository. Instead, the Corda Enterprise The Corda Enterprise binaries are not available in a publicly accessible Maven repository. Instead, the Corda Enterprise
binaries will be made available to your organisation as a tarball (``corda-3.0-developer-pack.tar.gz``). binaries will be made available to your organisation as a compressed tarball (``corda-3.1-developer-pack.tar.gz``).
This tarball contains all of the Corda dependencies as they would appear in your local Maven repository located at This tarball contains all of the Corda dependencies as they would appear in your local Maven repository located at
``~/.m2/repository``. ``~/.m2/repository``.
@ -187,13 +187,13 @@ dependencies.
c. Add Corda Enterprise binaries to a local directory and register a local Maven repository pointing to this directory with Gradle. c. Add Corda Enterprise binaries to a local directory and register a local Maven repository pointing to this directory with Gradle.
.. note:: Upon receiving the binaries, the quickest way to get started developing your CorDapps is **option a**. This can .. note:: Upon receiving the binaries, the quickest way to get started developing your CorDapps is **option a**. This can
be done by firstly unpacking the ``corda-3.0-developer-pack.tar.gz`` tarball: be done by firstly unpacking the ``corda-3.1-developer-pack.tar.gz`` compressed tarball:
``tar -xvf corda-3.0-developer-pack.tar.gz`` ``tar -xvzf corda-3.1-developer-pack.tar.gz``
Then, copy the unpacked ``respository`` folder to your local Maven repository: Then, copy the unpacked ``respository`` folder to your local Maven repository:
``rsync -av repository ~/.m2/repository`` ``rsync -av repository ~/.m2/``
The extracted folder can now be deleted: The extracted folder can now be deleted: