The CobiGen repository is organized in a one-branch-per-plugin schema. By that, we can release each plug-in continously and independently without side effects. On release the plug-in branch is merged to master branch such that you will find all the latest releases of each plug-in on the master branch.
Top-level folder | Description |
---|---|
|
Contains git submodules for building and tagging the wiki. |
|
Contains the cobigen eclipse bundles. The implementation of the plug-in is driven in |
|
Contains the maven plug-in implementation. |
|
Project to be used for AgileReview |
|
Sample code to be used for CobiGen demonstrations |
|
Contains template sets for different architectures |
|
Containts the code implementation of CobiGen as well as all plug-in implementations besides the eclipse plug-in and maven plug-in |
|
Contains the shared settings processed by the oasp4j-ide |
You can build CobiGen core as well as each plug-in besides the eclipse plug-in separately by stepping into the plug-in folder, e.g. for the Java plug-in you could step into cobigen/cobigen-javaplugin
and run mvn clean install
to build the plug-in and deploy it into your local repository.
The CobiGen eclipse plug-in can build build by running mvn clean package -Pp2-build-mars
. The profile p2-build-mars
builds the eclipse plug-in by retrieving eclipse mars bundles as dependencies. Without specifying the profile, the build will fail. An exception to this is the cobigen-eclipse-test project, which has to be built using mvn clean package -Pp2-build-mars,p2-build-stable,p2-build-experimental
.
CobiGen deployment has to be distinguished threefold
Component | Deployment Type | Commands |
---|---|---|
|
MAVEN |
|
|
ECLIPSE |
|
|
ECLIPSE |
|