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 the cobigen command line interface implementation. |
|
Contains the cobigen eclipse integration. The implementation of the plug-in is driven in |
|
Contains the maven integration implementation. |
|
Contains template sets for different architectures |
|
Containts the code implementation of CobiGen |
|
core plug-in implementations |
|
Contains the shared settings processed by the devonfw-ide |
To debug Maven builds on any plug-in:
-
Step into the plug-in and start a console there.
-
Run
mvnDebug clean install, it will output the port the debugger is listening to. -
On Eclipse, right click your project → Debug as → Debug Configurations…
-
Add a new Remote Java Application that connects on a socket on the port that was outputted by Maven.
-
Hit debug and have fun!
To debug Maven tests follow this link
The source code and maven bundles are released under APL 2.0
Eclipse bundles are released with respect to it’s bundled OSS software licenses