From: Jeff Garzik <jgarzik@bitpay•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] How to create a pull tester JAR
Date: Tue, 5 Aug 2014 11:45:35 -0400 [thread overview]
Message-ID: <CAJHLa0NdJhGyFfhzhxmL3=qNjYed0+FQ-X4EQdrVMR3K4Het7Q@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP1mU6iS6NRyK6iJtg4BEQ3nQRFc-dVwaOd+P_NFThqxjw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3141 bytes --]
Thanks for posting that (and implicitly archiving the knowledge). Anything
that makes test improvement easier is welcomed.
On Tue, Aug 5, 2014 at 11:00 AM, Mike Hearn <mike@plan99•net> wrote:
> I just checked in a change to bitcoinj git master that makes it much
> easier to create a pull tester jar. Here are instructions for how to do it.
>
> You will need:
>
> - A Java Development Kit (JDK), version 6 or up should work. As Java 6
> was released eight years ago, this should not be a challenging requirement.
> If you have a Mac just running "java" from the command line should give you
> a GUI prompt to install it automatically. Otherwise apt-get or fetch the
> latest from the interwebs.
>
> - Apache Maven. This is a rough equivalent of autotools, except it
> does dependency resolution for you. Grab it from
> http://maven.apache.org/download.cgi then unzip it and make sure the
> bin directory is in your PATH. You may need to set the JAVA_HOME
> environment variable if you installed Java to an odd place.
>
> - git
>
> Make sure you can run "javac" from the command line, then make sure you
> can run "mvn", it should complain it can't find a POM (this is a build
> config file) and not, say, that it can't find Java.
>
> Now grab bitcoinj from git master:
>
> git clone https://github.com/bitcoinj/bitcoinj.git
>
> ... and build ....
>
> cd bitcoinj
> mvn -DskipTests package
>
> It will go off and download the libraries needed, compile, and create a
> bundled executable JAR called core/target/pull-tests.jar. This is sort of
> analogous to static linking in the Java world. It should be fast - expect a
> full build plus downloads to take less than a minute. You can use it either
> with the QA scripts in the bitcoin core qa/pull-tester directory or just
> run things directly:
>
> ./bitcoind -regtest -connect=0.0.0.0 -listen -whitelist=127.0.0.1
> -datadir=/tmp/pulltester
> java -jar core/target/pull-tests.jar
>
> It should go ahead and print lots of debug spew, then at the end say it's
> happy.
>
> Let me know if you encounter any problems with this.
>
> Java JARs (which are just zip files renamed) are easily reproduced if you
> use the same version of javac and the same bitcoinj version. The ZIP
> container has timestamps, but unzipping them and simply diffing the files
> between two builds should reveal no differences. I am happy to provide a
> pull-tests.jar from my local machine if anyone would like to do this.
>
>
> ------------------------------------------------------------------------------
> Infragistics Professional
> Build stunning WinForms apps today!
> Reboot your WinForms applications with our WinForms controls.
> Build a bridge from your legacy apps to the future.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
[-- Attachment #2: Type: text/html, Size: 4507 bytes --]
next prev parent reply other threads:[~2014-08-05 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 15:00 Mike Hearn
2014-08-05 15:11 ` Mike Hearn
2014-08-05 16:11 ` Andreas Schildbach
2014-08-05 15:45 ` Jeff Garzik [this message]
2014-08-05 16:58 ` Mike Hearn
2014-08-06 10:01 ` Jorge Timón
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJHLa0NdJhGyFfhzhxmL3=qNjYed0+FQ-X4EQdrVMR3K4Het7Q@mail.gmail.com' \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox