Events Development: Difference between revisions
Jump to navigation
Jump to search
Line 54: | Line 54: | ||
=How to add New Commands= | =How to add New Commands= | ||
This is how you code new clad commands: | |||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | <blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | ||
:[[Clad User Manual]] | :[[Clad User Manual]] | ||
</blockquote> | </blockquote> | ||
A few things to keep in mind: | |||
* The pipeline is initialized by the runtime, but there is no queue between the event processor and terminator. The command must install it. |
Revision as of 22:23, 21 April 2016
Internal
To clone:
git clone git@github.com:NovaOrdis/esa.git
TODO
doc/Event Development.docx TODO section.
Development
Unnumbered Development Release
This will install a new unnumbered (same release number) "development" release locally:
cdesa mvn clean install; ./bin/install -f
Numbered Release
1. Increment (or update) the version information from $PROJECT_HOME/pom.xml.
2. Build and install
-f is not necessary:
mvn clean install; ./bin/install
3. Check in
mvn clean git add . git commit -m "starting ... version" git push
Individual Unit Test
mvn -Dmaven.surefire.debug="-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5012" -Dtest=EventsApplicationRuntimeTest clean test
How to add New Commands
This is how you code new clad commands:
A few things to keep in mind:
- The pipeline is initialized by the runtime, but there is no queue between the event processor and terminator. The command must install it.