corda/gradle-plugins
Ross Nicoll ae2183c8a1 Reduce use of X500Name bridges (#1483)
* Change to using strings in CordformContext; X500Name is an external API dependency we're trying to avoid, X500Principal rearranges the order of the elements in a way we don't want, and trying to put CordaX500Name into Groovy in the time available is impractical. As such having pre-formatted strings used in the Cordform plugin makes most sense right now.
* Remove uses of CordaX500Name.x500
* Remove old X.500 parsing tools
* Move CordaX500Name.x500 into X500NameUtils
* Move X500NameUtils into internal
2017-09-14 11:56:14 +01:00
..
cordform-common Reduce use of X500Name bridges (#1483) 2017-09-14 11:56:14 +01:00
cordformation Reduce use of X500Name bridges (#1483) 2017-09-14 11:56:14 +01:00
publish-utils POMs generated by publishing are now correct. (#1055) 2017-07-18 12:34:56 +01:00
quasar-utils Demote quasar-core to a runtime dependency, and capsule to "compileOnly". (#1381) 2017-09-01 11:12:04 +01:00
build.gradle One demo definition for both IntelliJ and gradle (#697) 2017-05-18 15:58:35 +01:00
README.rst Don't start Corda webserver if no webAddress has been defined for a node (#1434) 2017-09-08 15:25:20 +01:00
settings.gradle Cordform common is now a part of the gradle plugin suite (#1474) 2017-09-12 19:18:09 +01:00

Gradle Plugins for Cordapps

The projects at this level of the project are gradle plugins for cordapps and are published to Maven Local with the rest of the Corda libraries.

Note

Some of the plugins here are duplicated with the ones in buildSrc. While the duplication is unwanted any currently known solution (such as publishing from buildSrc or setting up a separate project/repo) would introduce a two step build which is less convenient.

Version number

To modify the version number edit constants.properties in root dir

Installing

If you need to bootstrap the corda repository you can install these plugins with

cd publish-utils
../../gradlew -u install
cd ../
../gradlew install