Chris Beams f9bcd2abad
Resolve JUnit 4.10 vs. 4.11 classpath conflict
ethereumj-core depends on elements specific to the JUnit 4.11 API, but (for
reasons that can only be assumed dubious) json-simple:1.1.1 transitively
includes JUnit 4.10. At the command line, Gradle handles this cleanly,
and gives ethereumj-core's direct dependence on 4.11 the precedence it
deserves. However, IDEA gets confused and gives 4.10 precedence. This
change explicitly excludes the transitive dependency from
json-simple->junit:4.10, eliminating the issue completely.
2014-12-26 21:49:00 +01:00
..
2014-12-26 21:48:59 +01:00
2014-12-26 21:48:59 +01:00
2014-12-26 21:48:59 +01:00

ethereum-core

Include ethereum-core in your project

  1. Add http://dl.bintray.com/ethereum/maven as a repository to your build script
  2. Add a dependency on org.ethereum:ethereumj:$version, where $version is one of those listed at https://bintray.com/ethereum/maven/org.ethereum/view

Examples

See ethereumj-studio.

Build from source

Compile, test and package

Run ./gradlew build.

  • find jar artifacts at build/libs
  • find unit test and code coverage reports at build/reports

Run an ethereum node

  • run ./gradlew run, or
  • build a standalone executable jar with ./gradlew shadow and execute the -all jar in build/libs using java -jar [jarfile].

Import sources into IntelliJ IDEA

Use IDEA 14 or better and import project based on Gradle sources.

Note that in order to build the project without errors in IDEA, you will need to run gradle antlr4 manually.

Publish ethereumj-core builds

TODO: integrate bintray gradle plugin