fuse-quickstarts | Quick Starts and Demos

In order to keep the Quick Starts working and useful, there are some standards that all Quick Starts should adhere to.
Blueprint over Spring When developing Quick Starts, favor Blueprint XML over Spring DM. Blueprint XML is the recommended approach when using Karaf and the Spring DM framework is no longer maintained.
Java DSL over XML Use the Java DSL over XML based routes whenever possible as beginners generally find it easier to understand than the XML when coming from a Java background.
Provide Automated Tests Add Unit and Integration tests when appropriate.
Demonstrate both Sides of the Problem Quick Starts should demonstrate both the Producer and Consumer of the component when appropriate.
Provide Clear Instructions A README.md should be provided with requirements, set up steps, steps to run, and expected output. Additional explanations can be provided as needed.
Keep it Simple Quick Starts should be kept as simple as possible. In most cases, this means not much more complex than the examples found in the documentation. This is to ensure that they are easily understood by developers at all levels. Quick Starts that are inherently more complex should be noted.
Follow Maven Best Practices All Quick Starts should use the relevant Parent POM's that already exist within the project and update them with new dependencies as needed.