Enhance CONTRIBUTING.md with toc and update build steps

Added TOC for navigation
updated build instructions and added log creation

Signed-off-by: Peter Kirschner <peter@klib.io>

Author: peterkir

CONTRIBUTING.md

@@ -2,6 +2,31 @@
 
 Want to hack on Bnd/Bndtools? Here are instructions to get you started. They are probably not perfect, please let us know if anything feels wrong or incomplete.
 
+## Table of Contents
+
+- [Reporting Issues](#reporting-issues)
+- [Development Setups](#development-setups)
+- [Launching Bndtools from Eclipse](#launching-bndtools-from-eclipse)
+- [Manually Building Bndtools](#manually-building-bndtools)
+  - [Checking Out from GitHub](#checking-out-from-github)
+  - [Building from the command-line](#building-from-the-command-line)
+  - [Importing Into Eclipse](#importing-into-eclipse)
+- [Running single tests](#running-single-tests)
+- [Build Environment](#build-environment)
+  - [Gradle Wrapper](#gradle-wrapper)
+- [Running JUnit Tests](#running-junit-tests)
+- [Workflow](#workflow)
+  - [Setting up the triangular workflow](#setting-up-the-triangular-workflow)
+- [Contribution guidelines](#contribution-guidelines)
+  - [Pull requests are always welcome](#pull-requests-are-always-welcome)
+  - [Create issues](#create-issues)
+  - [But check for existing issues first](#but-check-for-existing-issues-first)
+  - [Conventions](#conventions)
+  - [Large changes/Work-In-Progress](#large-changeswork-in-progress)
+  - [Sign your work](#sign-your-work)
+  - [Merge approval](#merge-approval)
+  - [How can I become a maintainer](#how-can-i-become-a-maintainer)
+
 ## Reporting Issues
 
 When reporting [issues](https://github.com/bndtools/bnd/issues) on GitHub please include the version of Bnd/Bndtools you are using, `bnd version`, as well as the version of Java, `java -version`, and your OS.
@@ -87,21 +112,49 @@ You should now have all the bndtools projects in your workspace, ready to begin
 ## Build Environment
 
 The only thing you need to build Bnd/Bndtools is Java.
-- We require at least Java 17.
-- We use Gradle and Maven to build and the repo includes `gradlew` and `mvnw` at the necessary versions.
-
-- `./gradlew :build` (or `./gradlew build -x test -x testOSGi` to skip tests for faster local builds) - Assembles and tests the Bnd Workspace projects. This must be run before building the Bnd Maven and Gradle plugins.
-- `./gradlew :gradle-plugins:build` - Assembles and tests the Bnd Gradle plugins.
-- `./mvnw install` - Assembles and tests the Bnd Maven plugins.
-- `./gradlew :publish` - Assembles and publishes the Bnd Workspace projects into `dist/bundles`.
-- `./gradlew :gradle-plugins:publish` - Assembles and publishes the Bnd Gradle plugins into `dist/bundles`.
-- `./mvnw -Pdist deploy` - Assembles and publishes the Bnd Maven plugins into `dist/bundles`.
+- We require at least Java 17 locally installed in path.
+- We use Gradle and Maven to build and the repo includes `gradlew` and `mvnw` wrappers with the necessary versions.
+
+- assembles and tests the Bnd Workspace projects
+  ```bash
+  ./gradlew build 2>&1 | tee "build_$(date +%Y%m%d_%H%M%S).log"
+  ```
+- alternative skip tests for faster local builds 
+  ```bash
+  ./gradlew build -x test -x testOSGi 2>&1 | tee "build_skipTests_$(date +%Y%m%d_%H%M%S).log"
+  ```
+**MIND: Above step is pre-requisite for following build of Bnd Maven and Gradle plugin.**
+- assembles and tests the Bnd Gradle plugins
+  ```bash
+  ./gradlew :gradle-plugins:build 2>&1 | tee "build_gradle-plguns_$(date +%Y%m%d_%H%M%S).log"
+  ```
+- assembles and tests the Bnd Maven plugins
+  ```bash
+  ./mvnw install 2>&1 | tee "build_mvn_$(date +%Y%m%d_%H%M%S).log"
+  ```
+- assembles and publishes the Bnd Workspace projects into `dist/bundles`
+  ```bash
+  ./gradlew publish 2>&1 | tee "build_publish_$(date +%Y%m%d_%H%M%S).log"
+  ```
+- assembles and publishes the Bnd Gradle plugins into `dist/bundles`
+  ```bash
+  ./gradlew :gradle-plugins:publish 2>&1 | tee "build_gradle-plugins_publish_$(date +%Y%m%d_%H%M%S).log"
+  ```
+- assembles and publishes the Bnd Maven plugins into `dist/bundles`
+  ```bash
+  ./mvnw -Pdist deploy 2>&1 | tee "build_mvn_deploy_$(date +%Y%m%d_%H%M%S).log"
+  ```
 
 Rebuilding: bnd is built with bnd. For that reason we rebuild and retest bnd with the build we just built.
 To do a full build-rebuild cycle (like the github build), you can use the following command:
 
-`.cd /gradlew :build ; ./gradlew :gradle-plugins:build ; ./.github/scripts/rebuild-build.sh ; ./.github/scripts/rebuild-test.sh`
-
+```
+./gradlew build \
+  && ./gradlew :gradle-plugins:build \
+  && ./.github/scripts/rebuild-build.sh \
+  && ./.github/scripts/rebuild-test.sh \
+  2>&1 | tee "build_full_$(date +%Y%m%d_%H%M%S).log"
+```
 
 We use [GitHub Actions](https://github.com/bndtools/bnd/actions?query=workflow%3A%22CI%20Build%22) for continuous integration and the repo includes a `.github/workflows/cibuild.yml` file to build via GitHub Actions.
 
@@ -305,4 +358,3 @@ If your pull request was originally a work-in-progress, don't forget to remove W
 Don't forget: being a maintainer is a time investment.
 Make sure you will have time to make yourself available.
 You don't have to be a maintainer to make a difference on the project!
-