Commit Graph

14 Commits

Author SHA1 Message Date
Adrian Tiberius 1d3782c3be Added android app wrapper 2015-04-28 20:14:10 +03:00
eugene-shevchenko b823521882 VM trace creation listener added. 2015-04-02 17:59:13 +03:00
eugene-shevchenko 8fd961ecaf version up 2015-03-27 10:53:05 +02:00
Roman Mandeleil 2c2a0f2f37 Reduce warning noise 2015-03-17 00:30:07 +02:00
Roman Mandeleil c8aadee01e Bump basic version 2015-03-16 19:40:55 +02:00
Roman Mandeleil bed4e9f8a8 upgrade to POC-8 2015-01-14 11:42:19 +02:00
Chris Beams cf84648ea9
Fix error in UTF-8 compilation config 2014-12-30 22:05:50 +01:00
Chris Beams d54b65f398
Specify explicit UTF-8 encoding for compilation
UTF-8 is the default file encoding on some platforms (e.g. OS X), but
for other platforms (e.g. Windows), UTF-8 characters in classes like
ECKey cause errors during compilation on other platforms (e.g. Windows).

See http://pastebin.com/X9jEemje for examples of these errors.

This commit configures Gradle to explicitly use UTF-8 encoding for all
compilation tasks.
2014-12-30 21:54:36 +01:00
Chris Beams 936de35cff
Restore JDK 8 source compatibility in ethereumj-studio
This partially reverts commit c95f5ea, restoring use of Java 8 language
features and APIs to ethereumj-studio, while leaving etherumj-core
pinned to the Java 7 language level for Dalvik compatibility reasons.
For further details, see the prior commit and
https://github.com/ethereum/ethereumj/commit/c95f5ea#commitcomment-9119435.
2014-12-30 20:09:20 +01:00
Roman Mandeleil c95f5ea75f reverting for java7 2014-12-30 13:45:16 +02:00
Roman Mandeleil f11787ce59 there will be no 0.7.15 2014-12-29 14:54:00 +02:00
Chris Beams 366f6246ce
Upgrade to JDK 8 compatibility
As of this commit, JDK 8 or better is required to compile or run against
ethereumj.
2014-12-27 03:53:34 +01:00
Chris Beams 75443aaa13
Support running ethereumj-studio as executable jar
See updated ethereumj-studio/README.md for details. Note that this
commit removes the `build-post-package.xml` ant file (for now) to
simplify the Gradle arrangement. This functionality can be re-introduced
later and more simply using Gradle's native DSL. In the meantime, both
the -core and -studio projects can be run using `gradle run` or run as
executable jars by running `gradle shadowJar` followed by the usual
`java -jar` execution of the resulting `-all` jar file found in each
project's respective `build/libs` directory.
2014-12-27 01:44:25 +01:00
Chris Beams 0900039bdd
Introduce top-level Gradle build
- Convert ethereumj-studio build from Maven to Gradle as well
 - Extract common build elements to top-level build.gradle
 - Update top-level README accordingly
2014-12-27 01:44:24 +01:00