Upgrade to xtext2.4 (again)
RIM grammar improvement to contain resource within a block defined by '{' and '}'
RIM grammar improvement to identity the resource type and resource entity in a more readable way 'type:' and 'entity:'
RIM grammar improvement to contain event and command within a block defined by '{' and '}'.  Command currently makes usage of the block '{}' optional.
Updated all the examples following the first round of upgrades to the RIM grammar.
Minor fix to a couple of test RIMs.
Added license plugin ignore to keep eclipse happy.
Initial implementation of useragent-swagger-ui.  A simple maven war project to enable IRIS examples to include the swagger ui, the only change from https://github.com/wordnik/swagger-ui/tree/master/dist is the rename of index.html to swagger.html to let it coexist with the other user agent examples.  swagger.jsp is probably not required, but at one point it looked as though the swagger ui would not work in chrome without these CORS headers.
Initial implementation of an additional xtext generator for swagger.
Minor correction to conform to web.xml schema.
Fix the repository location in the SDK archetype.
Remove a duff character from the DataJSCRUD.js that stopped the default navigator working.
Update the SDK archetype, we don't want the RIM generated source to end up in src/main/java
Initial commit of the Restbucks coffee shop example, straight after generation of the mockresponder with the interaction sdk.
Add support for auto and foreach transitions in RIM visualisation
Improve the transition descriptions in RIM visualisation
Correct a minor issue with the duplication of RIM transition descriptions
Turned the Restbucks generated Data Service into an Interaction Service.  Also added the HALProvider to the example.
Fix a minor issue with the simple examples jetty configuration when building the entire project.
Added initial support for the auto transition to a state with links.  Prior to this change the auto transition to another state did not only not fetch the target state, but most importantly it didn't attempt to render the target states links.  More work is required to support the transition properties as currently any path parameters in the target can only be resolve from the entity and effectively the auto transition will only work if the target entity is the same type as the source entity.