Commit 6f036f9c authored by Mike Hearn's avatar Mike Hearn

s/BitCoinJ/bitcoinj/ everywhere except the version handshake.

Resolves issue 249.
parent 9cc9607c
......@@ -19,7 +19,7 @@
<Class name="~org\.bitcoinj\.wallet\.Protos.*"/>
</Match>
<!-- BitCoinJ is not designed to run in an environment with malicious code loaded into the VM -->
<!-- bitcoinj is not designed to run in an environment with malicious code loaded into the VM -->
<Bug category="MALICIOUS_CODE"/>
<!-- This is flagging a valid issue but the real bug is in the JDK. See issue 173. -->
......
......@@ -149,7 +149,7 @@
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
</dependency>
<!-- BitCoinJ consumers are expected to provide their own SLF4J adapters
<!-- bitcoinj consumers are expected to provide their own SLF4J adapters
such as logback, slf4j-log4j12, slf4j-jcl and so on
see http://www.slf4j.org/faq.html -->
<dependency>
......
......@@ -162,7 +162,7 @@ public class PeerGroup {
// - using connectTo() will increment it by one
this.maxConnections = 0;
// Set up a default template version message that doesn't tell the other side what kind of BitCoinJ user
// Set up a default template version message that doesn't tell the other side what kind of bitcoinj user
// this is.
this.versionMessage = new VersionMessage(params, chain.getBestChainHeight());
......
......@@ -98,7 +98,7 @@ public class IrcDiscovery implements PeerDiscovery {
BufferedReader reader = new BufferedReader(new InputStreamReader(connection.getInputStream(), "UTF-8"));
// Generate a random nick for the connection. This is chosen to be clearly identifiable as coming from
// BitCoinJ but not match the standard nick format, so full peers don't try and connect to us.
// bitcoinj but not match the standard nick format, so full peers don't try and connect to us.
String nickRnd = String.format("bcj%d", new Random().nextInt(Integer.MAX_VALUE));
String command = "NICK " + nickRnd;
logAndSend(command);
......
......@@ -42,7 +42,7 @@ import java.util.Map;
* a data interchange format developed by Google with an efficient binary representation, a type safe specification
* language and compilers that generate code to work with those data structures for many languages. Protocol buffers
* can have their format evolved over time: conceptually they represent data using (tag, length, value) tuples. The
* format is defined by the <tt>bitcoin.proto</tt> file in the BitCoinJ source distribution.<p>
* format is defined by the <tt>bitcoin.proto</tt> file in the bitcoinj source distribution.<p>
*
* This class is used through its static methods. The most common operations are writeWallet and readWallet, which do
* the obvious operations on Output/InputStreams. You can use a {@link java.io.ByteArrayInputStream} and equivalent
......
......@@ -103,7 +103,7 @@
<mailingLists>
<mailingList>
<name>BitCoinJ Google Group</name>
<name>bitcoinj Google Group</name>
<post>https://groups.google.com/forum/#!forum/bitcoinj</post>
</mailingList>
</mailingLists>
......@@ -176,7 +176,7 @@
<artifactId>slf4j-api</artifactId>
<version>${slf4j.version}</version>
</dependency>
<!-- BitCoinJ consumers are expected to provide their own SLF4J adapters
<!-- bitcoinj consumers are expected to provide their own SLF4J adapters
such as logback, slf4j-log4j12, slf4j-jcl and so on
see http://www.slf4j.org/faq.html -->
<dependency>
......
......@@ -29,7 +29,7 @@
<artifactId>bitcoinj-tools</artifactId>
<name>bitcoinj Tools</name>
<description>A collection of useful tools that use the BitCoinJ library to perform wallet operations</description>
<description>A collection of useful tools that use the bitcoinj library to perform wallet operations</description>
<build>
<plugins>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment