Allocating more memory for importing project with tools/run

More memory can be allocated using MINGLE_ARGS. Most of the steps are the same as that listed in Readme except for some small modifications.

Steps to import

Advantage of this approach is that a detailed output will be logged to screen and it will be very easy to track the line of code corresponding to the error (if any).

Step #1: Update broker.yml
THE IMPORT PROCESS REQUIRES THAT THE MINGLE SERVER BE CONFIGURED WITH A TCP CONNECTOR FOR ACTIVEMQ. TO CONFIGURE THIS:
* STOP THE MINGLE SERVER.
* IN THE broker.yml FILE INSIDE THE CONFIG SUBFOLDER OF YOUR MINGLE DATA DIRECTORY, e.g. <MINGLE_DATA_DIR>/CONFIG, COMMENT OUT THE VM OPTION LINE AND UNCOMMENT THE TCP OPTION LINE.
As an example, I commented this line as follows on my windows machine:
#uri: vm://localhost?create=false&jms.prefetchPolicy.all=0
TAKE NOTE OF THIS CHANGE, AS IT HAS TO BE REVERTED AFTER THE USE OF import_projects.rb.

No need to have Mingle server running. The tools/run command does not require Mingle server to be running.

Before running the tools/run command, allocate more memory to the process by running :
$export MINGLE_ARGS=-Xmx2048m
When the script finishes, unset with
$export MINGLE_ARGS=

 Step #2 : Move the exported project to appropriate folder

Create a folder called exported_projects at <MINGLE_HOME>/exported_projects

Step #3 : Run import from command line

* Identify the directory where Mingle is installed. Let's call this MINGLE_HOME.
* Identify the Mingle data directory. This is the --mingle.dataDir property is supplied when starting the Mingle server. Let's call this MINGLE_DATA_DIR.
* At the terminal, navigate to <MINGLE_HOME>
* Make the tools/run file executable with this command: chmod +x tools/run
* Use the run script to start import_projects.rb running by using the following command: tools/run tools/export_import/import_projects.rb --mingle.dataDir=<MINGLE_DATA_DIR>

Since we copied only one project export in the <MINGLE_HOME>/exported_projects directory, it will import only one file. As the import is executed, it will log every step on screen up until the error. Please forward the entire text on screen to us. You may like to increase the size of screen buffers (height and width) to a large number so that the output text does not scroll away.

Step # 4 : Revert the changes made in step #1

TO DO THIS:
* STOP THE MINGLE SERVER.
* COMMENT OUT THE TCP OPTION IN broker.yml FOUND IN THE CONFIG SUBFOLDER OF YOUR MINGLE DATA DIRECTORY, UNCOMMENT THE VM OPTION LINE.
* RESTART MINGLE.