Updating documents and including cli features (&17)

Signed-off-by: Adam Knapp <adam.knapp@ericsson.com>

org.eclipse.titan.designer/docs/Eclipse_Designer_userguide/4-managing_projects.adoc

@@ -473,13 +473,13 @@ For TITAN Java projects there are different configuration options available.
 To set the project properties for local build first *right click* the project and select *Properties* then select *<<makefile-creation-attributes,TITAN Java Project Property>>*.
 
 [[the-internal-makefile-creation-attributes-tab-Java]]
-==== The Internal Makefile Creation Attributes Tab for TITAN Java Projects
+==== The Internal Build Attributes Tab for TITAN Java Projects
 
-image::images/4_F38_Internal_makefile_creation_attributes_for_TITAN_Java_Projects.png[title="Internal makefile creation attributes for TITAN Java Projects"]
+image::images/4_F38_Internal_makefile_creation_attributes_for_TITAN_Java_Projects.png[title="Internal build attributes for TITAN Java Projects"]
 
-On the Internal makefile creation attributes tab the options that configure the build process can be set. To change the value of an element it must be selected. Depending on the element selected on the left side, the right hand side of the tab will contain different options.
+On the Internal build attributes tab the options that configure the build process can be set. To change the value of an element it must be selected. Depending on the element selected on the left side, the right hand side of the tab will contain different options.
 
-NOTE: In TITAN Java Projects the build system is not using makefiles, the name was kept to be compatible with the TITAN Project look and feel.
+NOTE: In TITAN Java Projects the build system is not using makefiles, but this tab resembles the Internal makefile creation attributes of TITAN Projects.
 
 . TTCN-3 Preprocessor
 
@@ -855,6 +855,19 @@ Available options:
 
 * *Limit the number of parallel import processes:* During the import procedure several threads are created to utilize the parallelism of modern CPUs and improve performance. However, in some cases the number of created threads exceeds the OS or the user thread/process limit that results in Out Of Memory exception. This option limits the number of parallel processes to the number of native threads provided by the CPU.
 
+[[cli-import]]
+=== Importing Projects from the Command Line
+
+It is possible to invoke the import process of Eclipse from the command line, without Eclipse showing even the splash screen. The project to import must be an Eclipse project, i.e. the project folder has to contain `.project` and `.TITAN_properties` project descriptor files. The main use case of this import method is to bring the project into the specified workspace without modifying the file system.
+If the project already exists in the selected workspace, i.e. there is a project in the workspace with the same name, the import will be not executed. This way both TITAN C/C++ and TITAN Java projects can be imported into the specified workspace.
+
+An example invocation:
+[source]
+----
+eclipse.exe -noSplash -consoleLog -data location_of_workspace -application org.eclipse.titan.designer.application.ImportProject location_of_project_folder
+----
+
+
 === Useful Tips for Exporting and Importing
 
 [[pitfalls-1]]

org.eclipse.titan.designer/docs/Eclipse_Designer_userguide/6-building_the_project.adoc

@@ -183,9 +183,16 @@ eclipse.exe -noSplash -consoleLog -data location_of_workspace -application org.e
 ----
 
 This command instructs Eclipse to call our application with the name of the project to be built, while not displaying even the splash screen, redirecting all error log to the console too and using the workspace from the provided location.
+The project must be available in the specified workspace. If it is not, then it could be imported with a different command line application (see <<4-managing_projects.adoc#cli-import, Importing Projects from the Command Line>>). This way both TITAN C/C++ and TITAN Java projects can be built. 
 
 The benefit of using this feature over generating the Makefile and building by hand is that this way one will build with the exact same settings he uses inside Eclipse. If for example 3rd party tools are also used as part of the build process, this method will invoke them too properly.
 
+Furthermore, TITAN Java projects can be automatically exported as runnable JAR files at the end of the build process:
+[source]
+----
+eclipse.exe -noSplash -consoleLog -data location_of_workspace -application org.eclipse.titan.designer.application.InvokeBuild project_name_to_build -jar path_to_jar
+----
+
 ==== Building with an External Script
 
 It is possible to create an XML file for each Eclipse project, which will store all the information needed to create the Makefile and build the project from the command line.