Events Development: Difference between revisions
Jump to navigation
Jump to search
m (Ovidiu moved page Esa Development to Events Development without leaving a redirect) |
|||
| Line 1: | Line 1: | ||
=Internal= | =Internal= | ||
* [[ | * [[events]] | ||
| Line 9: | Line 9: | ||
git clone git@github.com:NovaOrdis/esa.git | git clone git@github.com:NovaOrdis/esa.git | ||
</pre> | </pre> | ||
=TODO= | =TODO= | ||
Revision as of 01:42, 23 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.