Difference between revisions of "OS.bee Software Factory Installation Neon"

From OS.bee documentation
Jump to: navigation, search
(Installation of the Software Factory)
Line 1: Line 1:
== General information ==
=== Copyright Notice ===
{{Copyright Notice}}
=== License information ===
{{License information}}
== Installation of the Software Factory ==
== Installation of the Software Factory ==
Line 252: Line 244:
You can now continue with [[OS.bee Software Factory Samples]]
You can now continue with [[OS.bee Software Factory Samples]]
== General information ==
=== Copyright Notice ===
{{Copyright Notice}}
=== License information ===
{{License information}}

Revision as of 07:59, 5 July 2017

Installation of the Software Factory

Before you start

Java Version

To be able to use the OS.bee Software Factory, you need to have the right Java version installed.

On 64-bit Windows systems, this is Java JDK 8 64bit Java SE Downloads. If you have Java installed, there is generally a Java icon on the control panel which will enable you to find out the current version.

Eclipse Version

To be able to use the OS.bee Software Factory, you need to have the correct Eclipse Neon version installed. You can use Eclipse Neon 3 DSL Developers. Download and extract it to a folder location of your choosing. On Windows, we recommend C:\. This results in the installation folder C:\eclipse. This will be the assumed Eclipse installation folder for the rest of this document.

To be able to launch Eclipse easily, create a shortcut on the computer's desktop to the program C:\eclipse\eclipse.exe. Be sure to add the parameter -data /path/to/your/workspace to the shortcut's invocation of Eclipse in order to start in the correct workspace in the future. Otherwise, you will be prompted to specify a workspace each time you start Eclipse.

Make the following change to the eclipse.ini file found in the C:\eclipse folder:


This line allocates extra memory for Eclipse to use.

A resulting eclipse.ini file for a Windows installation might look like this:

<existing lines above>

OS.bee P2 Repository

At the moment, the installation is only possible if you have access to the internal network. Use this --> link directly in Eclipse.

Installation of the OS.bee Software Factory

  1. Start the new Eclipse installation and select or define a workspace. It is important that each Eclipse installation is assigned to its own workspace.


  2. Go to the menu bar and select Help -> Install New Software....


  3. Get the link to the repository from the download page, activate the checkbox if you agree to our Terms of Service and Use and if you are not a consumer. Click on one of the then activated buttons, copy the link and paste it into the field labeled Work with:. Then press Enter to make Eclipse load the content of the repository.


  4. Open the OS.bee Software Factory group, select the OS.bee Software Factory and click on Next.


  5. If during installation you encounter this, just hit Next.


  6. In the installation dialog, confirm the software to be installed by clicking on Next.


  7. Accept the terms of the license aggreement after reading them carefully, and then confirm the dialog by clicking on Finish.


  8. The installation will now begin. This may take a while, depending on your Internet connection speed.


  9. After the software has been downloaded, confirm the "Security Warning" dialog by clicking on OK.


  10. You will then be prompted to restart Eclipse. Please do so.


Set the Target Platform for the OS.bee Software Factory

  1. Check if the workspace you are using is the one you selected above when first opening Eclipse. If not, open the right one.

  2. Set the target platform here: Menu -> Window -> Preferences -> Plug-in Development -> Target Platform.

  3. Click on Add... to add a new target definition.


  4. Select "Default: ..." and click on Next.


  5. Click on Add... to add content, select "Software Site" and click on Next.


  6. Use the same URL previously saved to the clipboard for the Software Site.

  7. Open the group OS.bee Softwarefactory, select OS.bee Softwarefactory Targetplatform (DON'T INSTALL...),
    uncheck the Include required software checkbox and click on Finish.


  8. Change to register Content

    • Enter x.a in the filter and deactivate the following bundles in the resulting target definition:

      javax.annotation version 1.2
      javax.annotation.source version 1.2


    • Enter guava in the filter and deactivate the following bundle in the resulting target definition:

      com.google.guava version 21.0


    • Enter antlr in the filter and deactivate the following bundle in the resulting target definition:

      org.antlr.runtime version 4.3

      and click on finish.


  9. Do not forget to activate your newly created target definition!


  10. Restart Eclipse. You can use Menu -> File -> Restart to do so.

Set preferences in Eclipse

Git settings

Be sure to uncheck the automatic git-ignore for derived files, else generated files will not be checked in:

DS Annotations

  1. It is neccessary to activate the generation of descriptors based on DS Annotations
  2. Go to Window / Preferences in your Eclipse IDE
  3. Activate the "Generate descriptors from annotaded sources"


  4. Go to Window / Preferences in your Eclipse IDE, filter for "java" and go to Installed JREs and click on Search...


JDK Settings

  1. Locate your JDK (On Windows it's usually under C:\Program FIles\Java\...) and hit OK


  2. Select the newly added JDK and hit Apply, then OK


Maven Settings

For developers only!

Maven requires some settings in a file called settings.xml. The file is usually expected by Eclipse to be located in the .m2 directory in the Users home directory.

  1. You can start with the following content of the settings.xml (don't forget to replace the xxxx with the appropriate repo names):
     <?xml version="1.0" encoding="UTF-8"?>
     <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
    	xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
    	<!-- TODO: adapt the local path to your personal favourite -->
    		<!-- mirror | Specifies a repository mirror site to use instead of a given 
    			repository. The repository that | this mirror serves has an ID that matches 
    			the mirrorOf element of this mirror. IDs are used | for inheritance and direct 
    			lookup purposes, and must be unique across the set of mirrors. | <mirror> 
    			<id>mirrorId</id> <mirrorOf>repositoryId</mirrorOf> <name>Human Readable 
    			Name for this Mirror.</name> <url>http://my.repository.com/repo/path</url> 
    			</mirror> -->
    		<!-- not working mirrors p2: Gemini DBaccess maven: central.maven.org, -->
    			<id>Apache Mirror</id>
    	<!-- profiles | This is a list of profiles which can be activated in a variety 
    		of ways, and which can modify | the build process. Profiles provided in the 
    		settings.xml are intended to provide local machine- | specific paths and 
    		repository locations which allow the build to work in the local environment. 
    		| | For example, if you have an integration testing plugin - like cactus 
    		- that needs to know where | your Tomcat instance is installed, you can provide 
    		a variable here such that the variable is | dereferenced during the build 
    		process to configure the cactus plugin. | | As noted above, profiles can 
    		be activated in a variety of ways. One way - the activeProfiles | section 
    		of this document (settings.xml) - will be discussed later. Another way essentially 
    		| relies on the detection of a system property, either matching a particular 
    		value for the property, | or merely testing its existence. Profiles can also 
    		be activated by JDK version prefix, where a | value of '1.4' might activate 
    		a profile when the build is executed on a JDK version of '1.4.2_07'. | Finally, 
    		the list of active profiles can be specified directly from the command line. 
    		| | NOTE: For profiles defined in the settings.xml, you are restricted to 
    		specifying only artifact | repositories, plugin repositories, and free-form 
    		properties to be used as configuration | variables for plugins in the POM. 
    		| | -->
    				<!-- where to deploy the release artifacts -->
    				<!-- where to deploy the snapshot artifacts -->
    					<name>Compex Nexus Release</name>
    					<name>Compex Snapshots</name>
    					<name>Compex Nexus Snapshots</name>
    					<name>Compex Nexus Release</name>
    					<id>Compex Internal P2 OSbee</id>
    					<!-- use the URL you installed the softwarefactory from -->
    	<!-- activeProfiles | List of profiles that are active for all builds. | 
    		<activeProfiles> <activeProfile>alwaysActiveProfile</activeProfile> <activeProfile>anotherAlwaysActiveProfile</activeProfile> 
    		</activeProfiles> -->
  2. go to the Eclipse preferences / Maven / User Settings and enter the path to the settings.xml in the User settings section.

You can now continue with OS.bee Software Factory Samples

General information

Copyright Notice

All rights are reserved by Compex Systemhaus GmbH. In particular, duplications, translations, microfilming, saving and processing in electronic systems are protected by copyright. Use of this manual is only authorized with the permission of Compex Systemhaus GmbH. Infringements of the law shall be punished in accordance with civil and penal laws. We have taken utmost care in putting together texts and images. Nevertheless, the possibility of errors cannot be completely ruled out. The Figures and information in this manual are only given as approximations unless expressly indicated as binding. Amendments to the manual due to amendments to the standard software remain reserved. Please note that the latest amendments to the manual can be accessed through our helpdesk at any time. The contractually agreed regulations of the licensing and maintenance of the standard software shall apply with regard to liability for any errors in the documentation. Guarantees, particularly guarantees of quality or durability can only be assumed for the manual insofar as its quality or durability are expressly stipulated as guaranteed. If you would like to make a suggestion, the Compex Team would be very pleased to hear from you.

(c) 2019 Compex Systemhaus GmbH

License information

The OS.bee Software Factory is distributed under a commercial license.

The product itself is based on the OSBP Software Factory which is an Eclipse project. In addition, the software depends on several other open source projects, and the entire list of licenses used can be found here.