Decide whether to drop fabric8-annotations and fabric8-spring-boot from FIS 2.0

After a QE review of the fabric8-spring-boot component and a discussion with iocanel, we have come to question the suitability of the component for the FIS 2.0 release.

There are several arguments for dropping the component:

• Its use cases are already mostly covered by Spring Boot mechanisms or made redundant by Camel integrations with Spring Boot
• There are no quickstarts or examples on how to use fabric8-spring-boot
• There is no documentation on fabric8-spring-boot
• The only reasonable argument for keeping it is to have a way for FIS 1.0 fabric8-cdi users to migrate to spring boot, however,
  • fabric8-spring-boot does not implement all the features of the original fabric8-cdi (e.g. Endpoint injection is missing)
  • fabric8-cdi users would have to do a migration anyway, so they can as well migrate to a proper use of spring-boot

If we decide to keep fabric8-spring-boot (and fabric8-annotations), we need to solve these issues to make it supportable (write complete documentation, cover the features with examples and implement the missing features to be on feature-parity with fabric8-cdi and write a migration guide for fabric8-cdi users)

(note that some of fabric8-arquillian annotations are in fabric8-annotations, so they may have to be moved (or keep only those in fabric8-annotations))

rajdavies_jira acunning@redhat.com hchirino@redhat.com kcbabo Please decide, do we want to drop fabric8-spring-boot, or make it supportable?