From 3d92f5c8443ec956ba9057cac0ded932efe44d64 Mon Sep 17 00:00:00 2001
From: Joe Littlejohn <joelittlejohn@gmail.com>
Date: Thu, 16 May 2013 23:12:21 +0100
Subject: [PATCH] Reverting docs associated with 0.1.8 (will re-apply this
after the next release)
---
CHANGELOG.md | 4 ----
README.md | 4 +---
2 files changed, 1 insertion(+), 7 deletions(-)
diff --git a/CHANGELOG.md b/CHANGELOG.md
index ae012a3..ea88496 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,9 +1,5 @@
# embedmongo-maven-plugin Changelog
-## 0.1.8
-
-* Add support for random port allocation - new configuration option `randomPort`
-
## 0.1.7
* Add `logFile`/`logFileEncoding` configuration options (thanks @matthewadams)
diff --git a/README.md b/README.md
index 1d441ad..d8a7079 100644
--- a/README.md
+++ b/README.md
@@ -21,7 +21,6 @@ Usage
</goals>
<configuration>
<port>37017</port> <!-- optional, default 27017 -->
- <randomPort>true</randomPort> <!-- optional, default is false, if true overrides "static" port configuration -->
<version>2.0.4</version> <!-- optional, default 2.2.1 -->
<databaseDirectory>/tmp/mongotest</databaseDirectory> <!-- optional, default is a new dir in java.io.tmpdir -->
<logging>file</logging> <!-- optional (file|console|none), default console -->
@@ -49,8 +48,7 @@ Notes
* By default, the `start` goal is bound to `pre-integration-test`, the `stop` goal is bound to `post-integration-test`. You can of course bind to different phases if required.
* If you omit/forget the `stop` goal, any Mongo process spawned by the `start` goal will be stopped when the JVM terminates.
-* If you want to run many Maven builds in parallel you can use `randomPort` to avoid port conflicts.
- If you are using Jenkins, you can also try the [Port Allocator Plugin](https://wiki.jenkins-ci.org/display/JENKINS/Port+Allocator+Plugin).
+* If you want to run many Maven builds in parallel using Jenkins, try the [Port Allocator Plugin](https://wiki.jenkins-ci.org/display/JENKINS/Port+Allocator+Plugin) to avoid port conflicts.
* If you need to use a proxy to download MongoDB then you can either use `-Dhttp.proxyHost` and `-Dhttp.proxyPort` as additional Maven arguments (this will affect the entire build) or instruct the plugin to use a proxy when downloading Mongo by adding the `proxyHost` and `proxyPort` configuration properties.
* Using the `file` logging mode results in a new log file created at `./embedmongo.log` unless you specify via `<logFile>` (where `.` means the curent working directory, usually the same as `${basedir}`).
* If you'd like the start goal to start mongodb and wait, you can add `-Dembedmongo.wait` to your Maven command line arguments
--
GitLab