Extra detail about configuring build path (#15)

* Extra detail about configuring build path

* Include section on importing projects

* Rewording of import instructions

Author: ian-burnett

README.md

@@ -35,6 +35,14 @@ The sample Java classes are designed to be added to an OSGi bundle and deployed
 1. Copy the CICS supplied `DFHOSGI.jvmprofile` zFS file to the zFS directory specified by the `JVMPROFILE` SIT parameter, and ensure the `JAVA_HOME` variable is set correctly.
 1. Install the `DFHJVMS` resource defined in step 2 and ensure it becomes enabled.
 
+
+### Import the resources into your IDE
+
+1. Ensure you have an Eclipse-based IDE with the CICS Explorer SDK installed.
+1. Import the relevant projects into your Eclipse environment as described in [Adding the resources to Eclipse](/projects#adding-the-resources-to-eclipse).
+1. Follow the instructions in the [Generated resources](/projects#generated-resources) section to add any required binary libraries to the build path.
+
+
 ### To deploy the samples into a CICS region 
 
 1. Using the CICS Explorer export the `com.ibm.cicsdev.*.cicsbundle` projects to a zFS directory. The sample definitions use the following style of zFS location `/u/cics1/com.ibm.cicsdev.link.cicsbundle_1.0.0`.

projects/README.md

@@ -8,13 +8,16 @@ Complete Eclipse projects demonstrating how to use the JCICS API in an OSGi JVM
 
 * `com.ibm.cicsdev.*` - Eclipse project containing the Java source code.
 * `com.ibm.cicsdev.*.cicsbundle` - Eclipse project for a CICS bundle that can be deployed into a CICS region.
-* `com.ibm.cicsdev.*.resources.cicsbundle` - Eclipse project for a CICS bundle that defines the required program and transaction resources for the sample.
+* `com.ibm.cicsdev.*.resources.cicsbundle` - Eclipse project for a CICS bundle that defines the required
+program and transaction resources for the sample.
 
 
 ## Samples overview
 
-* [`com.ibm.cicsdev.link`](com.ibm.cicsdev.link) - Performing CICS LINK operations using both commareas, and channels and containers.
-* [`com.ibm.cicsdev.serialize`](com.ibm.cicsdev.serialize) - Serializing access to a common resource using the CICS ENQ and DEQ mechanism.
+* [`com.ibm.cicsdev.link`](com.ibm.cicsdev.link) - Performing CICS LINK operations using both commareas,
+and channels and containers.
+* [`com.ibm.cicsdev.serialize`](com.ibm.cicsdev.serialize) - Serializing access to a common resource using
+the CICS ENQ and DEQ mechanism.
 * [`com.ibm.cicsdev.tdq`](com.ibm.cicsdev.tdq) - Accessing transient data queues.
 * [`com.ibm.cicsdev.terminal`](com.ibm.cicsdev.terminal) - Reading in data from a terminal for an OSGi application.
 * [`com.ibm.cicsdev.tsq`](com.ibm.cicsdev.tsq) - Accessing temporary storage queues.
@@ -23,17 +26,20 @@ Complete Eclipse projects demonstrating how to use the JCICS API in an OSGi JVM
 
 ## Adding the resources to Eclipse
 
-1. Using an Eclipse development environment import the project from the project folder using the menu File -> Import -> Existing Projects into Workspace.
-1. Define and set a CICS Target Platform for the workspace using the menu Window -> Preferences -> Target Platform.
+1. Using an Eclipse development environment import the project from the project folder using the menu
+**File** -> **Import** -> **Existing Projects into Workspace**.
+1. Define and set a CICS Target Platform for the workspace using the menu **Window** -> **Preferences** ->
+**Target Platform**.
 
 
 ## Generated resources
 
-Several sample projects manipulate binary structures and utilize Java classes generated using the JZOS
-record generator. The generated classes can be found packaged in a jar file, found in the `lib/` subdirectory
-of the relevant project. Only the compiled helper classes are required to compile and run the application,
-however the generated source files are included for reference.
 
-If you are manually adding source files to your development environment, you will need to add the generated
-jar file to the classpath in order to compile the samples.
+The TS, TD, VSAM and LINK sample projects manipulate byte-oriented record structures using Java classes
+generated using the IBM Record Generator for Java. The generated classes can be found packaged in a JAR
+file, found in the `lib/` subdirectory of the relevant project.  Only the compiled helper classes are
+required to compile and run the application, however the generated source files are included for reference.
 
+If you are manually adding source files to your Eclipse development environment, you will need to add the
+generated JAR file to the build path in order to compile the samples, using the project context menu
+**Build Path** -> **Configure Build Path** -> **Libraries**.