-
Notifications
You must be signed in to change notification settings - Fork 70
mgmt_ide setup
We are using an own eclipse distribution as the oasp4j IDE does not cover eclipse plugin development features, we have to work with. To get started follow these steps:
-
Download the latest IDE release from https://coconet.capgemini.com/sf/go/projects.apps2_devon/frs.cobigen_development_distribution
-
Create a folder of your choice to store the IDE in. The folder should be located on the root of a drive to not run into "path too long" issues of Windows, which seemingly will never get fixed by Microsoft…
NoteAlternatively, you could also take a folder of your choice and map a new virtual drive to this folder, e.g. by http://www.ntwind.com/software/utilities/visual-subst.html
Using this solution, make sure, that you mount the folder of your choice permanently by selecting to mount the folder again on boot-time at the bottom of the dialog!Finally, copy the downloaded 7zip into the target folder and unzip with IMPORTANT! → "Extract Here":
The result should look like this:
-
Go to /workspaces/CobiGen and clone the repository. This tutorial utilizes TortoiseGit. However, you can also use any other tool like SourceTree or a simple GitBash to clone the CobiGen repository. Clone by triggering the explorer’s context menu:
Clone CobiGen’s repository recursively:
-
If cloning was successfull, run update-all-workspaces to start the automatic IDE setup:
The result should be something like this:
The folder structure generated until now should look like this:
The final list of scripts should be the following:
Mainly, there are two important scripts for your daily work. First, the console.bat script enables you to start a command line with a preconfigured PATH variable such that you will have the same experiences as in the eclipse IDE itself. Second, the eclipse-CobiGen.bat script will be the script you have to start your eclipse with. It will set the PATH before starting eclipse analogously to what console.bat does.
After setting up the IDE, we finally can start importing all necessary projects. The following steps just show the necessary tasks to do to get the master branch of CobiGen compiled and locally deployed and started in an eclipse distribution. There might be additional tasks to do if compiling any development branch (e.g. mvn install on the root of the cloned repository)
-
Start eclipse
-
Import the cobigen-core, all plugins, and cobigen-maven maven modules by triggering the context menu within the package explorer window:
-
Click Browse and press OK directly without chosing any folder (the default selected folder will do the job).
-
Select the modules to import
The result should look like this:NoteIf you face any issue select all projects and press Alt+F5 and confirm the dialog to update all maven projects. -
Now we have to import the cobigen-eclipse project, which has to be done quite differently due to many incompatibilies of the eclipse ecosystem with mvn. Select again Import in the Package Explorer's context menu and import a general project:
Press again browse as well as confirm the browse dialog without selecting anything as already done before. Select the cobigen-eclipse project:
-
After confirmation, you will end up with a cobigen-eclipse project struggling with classpath issues.
This is due to a workaround enabling the use of maven for eclipse plugin development. Thus, we have to make one manual step, whenever we will change the cobigen-eclipse/pom.xml. Run the command line from the IDE by utilizing StartExplorer on the cobigen-eclipse project:
You will end up in a command line at the location you run StartExplorer on via the context menu. -
Run mvn clean package. This should result in
and the cobigen-eclipse should build without any error.
That’s it! Finally, you can run the eclipse plugin by selecting the project and running it as an eclipse application. This will start a new eclipse application with the CobiGen eclipse plugin installed:
Disclaimer
If you discover any documentation bugs or would like to request new content, please raise them as an issue or create a pull request. Contributions to this wiki are done through the main repo under the folder documentation.
License
This documentation is licensed under the Creative Commons License (Attribution-NoDerivatives 4.0 International
)