svn commit: r1649912 - /incubator/nifi/site/trunk/content/development/quickstart.md

[jo...@apache.org]

Author: joewitt
Date: Tue Jan  6 19:03:37 2015
New Revision: 1649912

URL: http://svn.apache.org/r1649912
Log:
updated to reflect we no longer need the additional build step

Modified:
    incubator/nifi/site/trunk/content/development/quickstart.md

Modified: incubator/nifi/site/trunk/content/development/quickstart.md
URL: http://svn.apache.org/viewvc/incubator/nifi/site/trunk/content/development/quickstart.md?rev=1649912&r1=1649911&r2=1649912&view=diff
==============================================================================
--- incubator/nifi/site/trunk/content/development/quickstart.md (original)
+++ incubator/nifi/site/trunk/content/development/quickstart.md Tue Jan  6 19:03:37 2015
@@ -38,12 +38,10 @@ We're planning on revising these steps,
 
 1. You need a recent Java 7 JDK.
 2. You need Apache [Maven 3.X][maven]. We've successfully used 3.2.3 and as far back as 3.0.5
-3. Build the nar maven plugin.  In the root dir of the source tree cd to 'nar-maven-plugin'.
-   Run 'mvn clean install'
-4. Build the entire code base.  In the root dir of the source tree run 'mvn -T C1.0 clean install'
-   You can tweak the maven build settings as you like but the previous command will execute with 1 thread per core.
-5. Build the assembly/nifi application itself.  In the root dir of the source tree cd to 'assembly'.
-   Run 'mvn assembly:assembly'
+3. Build the nar maven plugin.  In the root dir of the source tree cd to `nar-maven-plugin`.
+   Run `mvn clean install`
+4. Build the entire code base.  In the root dir of the source tree run `mvn -T C2.0 clean install`
+   You can tweak the maven build settings as you like but the previous command will execute with 2 threads per core.
 
 Now you should have a fully functioning build off the latest code in the develop branch.
 
@@ -58,9 +56,9 @@ to 8080 is a good start, but on systems
 
 #### Decompress and launch
 
-`mvn assembly:assembly` will create a tar.gz file in the target directory in `assembly`. This tar.gz should
+Running the above build will create a tar.gz (and zip) file in `assembly/target`. This tar.gz should
 contain the full application. Decompressing the tar.gz should make a directory for you containing several other
-directories. `conf` contains application configuration, `logs` will contain log files, `bin` contains scripts
+directories. `conf` contains application configuration, `bin` contains scripts
 for launching the application. On linux and OSX, NiFi can be run using `bin/nifi.sh <command>` where
 `<command>` is one of: