Skip to content

devonfw/cobigen

master
Switch branches/tags
Code

Latest commit

* #1526 added new Eclipse text input test
added a test which tests a simple generate from text input
added a new processCobiGenWithTextInput method to EclipseCobiGenUtils
refactored processCobiGen method
added new generateWithSelectedIncrements method to EclipseCobiGenUtils

* #1526 fixed infinite loop
wrapped getActiveWorkbenchWindow into asynchronous runnables
added workbenchWindow class variable
added extra check for FileEditorInput

* #1526 added missing files
added .classpath and .project files

* #1526 fixed Eclipse crash
changed asynchronous runnable to synchronized
46bb194

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time

CobiGen (Code-based incremental Generator)

https://maven-badges.herokuapp.com/maven-central/com.devonfw.cobigen/cobigen-maven-plugin Build Status

Installation

Repository Organization

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

cobigen-cli

Contains the cobigen command line interface implementation.

cobigen-eclipse

Contains the cobigen eclipse integration. The implementation of the plug-in is driven in cobigen-eclipse/cobigen-eclipse folder.

cobigen-maven

Contains the maven integration implementation.

cobigen-templates

Contains template sets for different architectures

cobigen

Containts the code implementation of CobiGen

cobigen-plugins

core plug-in implementations

Build

bash build.sh (on windows use git bash)

Deploy

CobiGen deployment will be done by CI/CD only. No manual deployment.

Debugging with Maven

To debug Maven builds on any plug-in:

  1. Step into the plug-in and start a console there.

  2. Run mvnDebug clean install, it will output the port the debugger is listening to.

  3. On Eclipse, right click your project → Debug as → Debug Configurations…​

  4. Add a new Remote Java Application that connects on a socket on the port that was outputted by Maven.

  5. Hit debug and have fun!

To debug Maven tests follow this link

License

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