Docs: address review comments

This commit is contained in:
Mike Hearn 2019-02-21 11:07:23 +01:00
parent 01f0c4b3d2
commit c5c4df3037
2 changed files with 11 additions and 12 deletions

View File

@ -19,7 +19,7 @@ Version 4.0
* New configuration property ``database.initialiseAppSchema`` with values ``UPDATE``, ``VALIDATE`` and ``NONE``.
The property controls the behavior of the Hibernate DDL generation. ``UPDATE`` performs an update of CorDapp schemas, while
``VALID`` only verifies their integrity. The property does not affect the node-specific DDL handling and
``VALIDATE`` only verifies their integrity. The property does not affect the node-specific DDL handling and
complements ``database.initialiseSchema`` to disable DDL handling altogether.
* ``JacksonSupport.createInMemoryMapper`` was incorrectly marked as deprecated and is no longer so.
@ -305,7 +305,9 @@ Version 4.0
* Finance CorDapps are now built as sealed and signed JAR files.
Custom classes can no longer be placed in the packages defined in either finance Cordapp or access it's non-public members.
* Finance CorDapp was split into two separate apps: ``corda-finance-contracts`` and ``corda-finance-workflows``. There is no longer a single cordapp which provides both.
* Finance CorDapp was split into two separate apps: ``corda-finance-contracts`` and ``corda-finance-workflows``. There is
no longer a single cordapp which provides both. You need to have both JARs installed in the node simultaneously for the
app to work however.
* All sample CorDapps were split into separate apps: workflows and contracts to reflect new convention. It is recommended to structure your CorDapps
this way, see :doc:`app-upgrade-notes` on upgrading your CorDapp.
@ -339,5 +341,5 @@ Version 4.0
The only exception to this is ``Interpolator`` and related classes. These are now in the `IRS demo workflows CorDapp <https://github.com/corda/corda/tree/master/samples/irs-demo/cordapp/workflows-irs>`_.
* Vault states are now correctly migrated when moving from V3 to V4. In particular, this means the relevancy column is correctly filled, and the state party table is populated.
* Vault states are migrated when moving from V3 to V4: the relevancy column is correctly filled, and the state party table is populated.
Note: This means Corda can be slow to start up for the first time after upgrading from V3 to V4.

View File

@ -3,20 +3,17 @@ Getting set up for CorDapp development
Software requirements
---------------------
Corda uses industry-standard tools:
* **Oracle JDK 8 JVM** - minimum supported version **|java_version|** (please note that
* **Java 8 JVM** - we require at least version **|java_version|**, but do not currently support Java 9 or higher.
We have tested with Oracle JDK, Amazon Corretto, and Red Hat's OpenJDK builds. Please note that OpenJDK builds
usually exclude JavaFX, which our GUI tools require.
* **IntelliJ IDEA** - supported versions **2017.x** and **2018.x** (with Kotlin plugin version |kotlin_version|)
* **Git**
We also use Gradle and Kotlin, but you do not need to install them. A standalone Gradle wrapper is provided, and it
will download the correct version of Kotlin.
* **Gradle** - we use 4.10 and the ``gradlew`` script in the project / samples directories will download it for you.
Please note:
* Corda runs in a JVM. JVM implementations other than Oracle JDK 8 are not actively supported. However, if you do
choose to use OpenJDK, you will also need to install OpenJFX
* Applications on Corda (CorDapps) can be written in any language targeting the JVM. However, Corda itself and most of
the samples are written in Kotlin. Kotlin is an
`official Android language <https://developer.android.com/kotlin/index.html>`_, and you can read more about why
@ -131,7 +128,7 @@ Jetbrains offers a pre-built snap package that allows for easy, one-step install
.. _fedora-label:
Fedora
-------------
------
.. warning:: If you are using a Mac, Windows or Debian/Ubuntu machine, please follow the :ref:`mac-label`, :ref:`windows-label` or :ref:`deb-ubuntu-label` instructions instead.