Details
-
Enhancement
-
Resolution: Obsolete
-
Major
-
7.2.1
Description
We currently reuse the archetypes which come from the upstream projects like Apache Camel, Apache Karaf, etc.
Those archetypes are mostly very basic and some of them doesn't even provide a working example ootb. Also not every of these archetypes is deployable to a Karaf based runtime like JBoss Fuse.
A recent feedback from customer showed that the expected quality of those archetypes is not met and therefore needs to be improved.
My suggestions is:
- make our own archetypes with the help of runtime developers and maybe field engineers who are involved in common customer use cases
- keep those archetypes in Fuse Tooling code base
- the archetypes should be leaned towards real word use cases
- the archetypes should be more complex examples
- we should provide more information about the archetype in the creation wizard
- we should look at how JBoss currently does this and replicate for Fuse Tooling (see Quickstart Examples on JBoss side)