Updated typical development scenarios (markdown)

Robin Fleige commited 2018-08-17 10:44:47 +0000 commit afc19359789880f0eb9f2f939dba30537b9311ac

				wiki/info/landscape/typical-development-scenarios.md
			
          @@ -6,7 +6,7 @@

           We distinguish two cases: adding a 3rd-party bundle to the target platform and adding a new development bundle as a Java project.

           ## Adding a Bundle to the Target Platform

          -Add a New Library which can not be found in any SAP Repository

          +* Add a New Library which can not be found in any SAP Repository

           * Check if the library is already OSGi-enabled (normally this means there is a MANIFEST.MF file in the META-INF folder of the JAR file containing valid OSGi metadata.

           * In case the library is not OSGi-enabled someone has to create such a OSGi-enabled version (ask the technical lead of the project)

           * Add the library to an appropriate target folder under plugins/ in the project com.sap.sailing.targetplatform.base (e.g. target-base)

...	...	@@ -6,7 +6,7 @@
6	6	We distinguish two cases: adding a 3rd-party bundle to the target platform and adding a new development bundle as a Java project.
7	7
8	8	## Adding a Bundle to the Target Platform
9		-Add a New Library which can not be found in any SAP Repository
	9	+* Add a New Library which can not be found in any SAP Repository
10	10	* Check if the library is already OSGi-enabled (normally this means there is a MANIFEST.MF file in the META-INF folder of the JAR file containing valid OSGi metadata.
11	11	* In case the library is not OSGi-enabled someone has to create such a OSGi-enabled version (ask the technical lead of the project)
12	12	* Add the library to an appropriate target folder under plugins/ in the project com.sap.sailing.targetplatform.base (e.g. target-base)