Installing the CSDE

CSDE-cordapp-template-kotlin
repository in IntelliJ. If you are working with the CSDE-cordapp-template-java
repository, it looks very similar but the flow code is in a java
folder and the flow code is saved in more source files. For more information, see Java Flow Code.Downloading the CSDE

To obtain the CSDE template, clone the CSDE-cordapp-template-kotlin repository or CSDE-cordapp-template-java repository:
git clone https://github.com/corda/CSDE-cordapp-template-kotlin.git <local-folder>
git clone https://github.com/corda/CSDE-cordapp-template-java.git <local-folder>
Change to the new folder and create a new branch from the corda-5-0 release tag:
git checkout -b newbranch tags/release/corda-5-0
Initialise the Git repository and change the remote so you do not inadvertently push your work back to the R3 repository:
git init git remote add origin <remote-url>
where
<remote-url>
is the URL of the remote repository that you have created.Open the project in IntelliJ and let the import process complete. When complete, the project structure looks as follows:
CSDE project
Configuring the CSDE

The CSDE includes Gradle tasks to manage a local deployment of Corda. These Gradle tasks require Java Azul Zulu 11. To configure IntelliJ to use the correct Java version for Gradle, set Gradle JVM to Project SDK 11, via File > Settings > Build, Execution, Deployment > Build Tools > Gradle.


If using IntelliJ IDEA version 2023.1.4 or greater, then you should instead set the environmental variable JAVA_HOME
to point to your installation of Java Azul Zulu 11.
Was this page helpful?
Thanks for your feedback!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.
We're sorry this page wasn't helpful. Let us know how we can make it better!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Create an issue
Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.